BuildJet Outage History

BuildJet is up right now

Pingoru has recorded 31 incidents for BuildJet: 6 in the last 12 months and 0 in the last 90 days.

Source: status.buildjet.com

31incidents recorded
6last 12 months
0last 90 days
23 daystypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking BuildJet in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20260326 of 720 (45%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 229 (0%)

Incidents, newest first

Major March 31, 2026 GitHub Actions Job Execution went down 136d

Started Mar 31, 2026, 01:57 PM UTC· resolved Aug 14, 2026, 02:33 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 5, 2026 Incident with Github Actions 53m Current status by service (GitHub Actions Job Execution)

Started Mar 05, 2026, 10:56 PM UTC· resolved Mar 05, 2026, 11:49 PM UTC

  1. investigating Mar 05, 2026, 10:56 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/g9j4tmfqdd09

  2. resolved Mar 05, 2026, 11:49 PM UTC

    This incident has been solved by GitHub.

Read the full incident report →

Minor March 5, 2026 Incident with Github Actions 2h 28m Current status by service (GitHub Actions Job Execution)

Started Mar 05, 2026, 04:40 PM UTC· resolved Mar 05, 2026, 07:08 PM UTC

  1. investigating Mar 05, 2026, 04:40 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/g5gnt5l5hf56

  2. resolved Mar 05, 2026, 07:08 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor February 4, 2026 Incident with BuildJet for GitHub Actions 7m Current status by service (GitHub Actions Job Execution)

Started Feb 04, 2026, 09:30 AM UTC· resolved Feb 04, 2026, 09:37 AM UTC

  1. investigating Feb 04, 2026, 09:30 AM UTC

    We are experiencing general degraded performance - only a subset of BuildJet for GitHub Actions users are impacted. We’re working to fix the problem as quickly as we can. We’ll share another update shortly.

  2. resolved Feb 04, 2026, 09:37 AM UTC

    We’re back! BuildJet for GitHub Actions is up and running. Please restart any pending GitHub Actions jobs with BuildJet runners.

Read the full incident report →

Minor January 15, 2026 Incident with Github Actions 1h 4m Current status by service (GitHub Actions Job Execution)

Started Jan 15, 2026, 02:27 PM UTC· resolved Jan 15, 2026, 03:31 PM UTC

  1. investigating Jan 15, 2026, 02:27 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/5ccghcfrkv39

  2. resolved Jan 15, 2026, 03:31 PM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor December 11, 2025 Incident with Github Actions 1h 53m Current status by service (GitHub Actions Job Execution)

Started Dec 11, 2025, 04:04 PM UTC· resolved Dec 11, 2025, 05:57 PM UTC

  1. investigating Dec 11, 2025, 04:04 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/xntfc1fz5rfb

  2. resolved Dec 11, 2025, 05:57 PM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor October 9, 2025 Incident with Github Actions 1h 32m Current status by service (GitHub Actions Job Execution)

Started Oct 09, 2025, 02:54 PM UTC· resolved Oct 09, 2025, 04:26 PM UTC

  1. investigating Oct 09, 2025, 02:54 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/k7bhmjkblcwp

  2. resolved Oct 09, 2025, 04:26 PM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor September 23, 2025 Incident with Github Actions 12m Current status by service (GitHub Actions Job Execution)

Started Sep 23, 2025, 05:32 PM UTC· resolved Sep 23, 2025, 05:44 PM UTC

  1. investigating Sep 23, 2025, 05:32 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/zlzvt6h3ck58

  2. resolved Sep 23, 2025, 05:44 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor August 27, 2025 Incident with Github Actions 18m Current status by service (GitHub Actions Job Execution)

Started Aug 27, 2025, 09:15 PM UTC· resolved Aug 27, 2025, 09:33 PM UTC

  1. investigating Aug 27, 2025, 09:15 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/x7gtw6r3x2s1

  2. resolved Aug 27, 2025, 09:33 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor August 19, 2025 Incident with Github Actions 2h 25m Current status by service (GitHub Actions Job Execution)

Started Aug 19, 2025, 01:48 PM UTC· resolved Aug 19, 2025, 04:13 PM UTC

  1. investigating Aug 19, 2025, 01:48 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/lgnmptjvcl5g

  2. resolved Aug 19, 2025, 04:13 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor August 12, 2025 Incident with Github Actions 4h 36m Current status by service (GitHub Actions Job Execution)

Started Aug 12, 2025, 02:17 PM UTC· resolved Aug 12, 2025, 06:53 PM UTC

  1. investigating Aug 12, 2025, 02:17 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/9rfydl2xdqqj

  2. resolved Aug 12, 2025, 06:53 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor August 5, 2025 Incident with Github Actions 35m Current status by service (GitHub Actions Job Execution)

Started Aug 05, 2025, 03:47 PM UTC· resolved Aug 05, 2025, 04:22 PM UTC

  1. investigating Aug 05, 2025, 03:47 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/6swp0zf7lk8h

  2. resolved Aug 05, 2025, 04:22 PM UTC

    Incident with Github Actions

Read the full incident report →

Minor July 21, 2025 Incident with Github Actions 2h 44m Current status by service (GitHub Actions Job Execution)

Started Jul 21, 2025, 07:18 AM UTC· resolved Jul 21, 2025, 10:02 AM UTC

  1. investigating Jul 21, 2025, 07:18 AM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/btl2cjm2pzkj

  2. resolved Jul 21, 2025, 10:02 AM UTC

    The incident has been resolved.

Read the full incident report →

Minor July 7, 2025 Incident with Github Actions 1h 38m Current status by service (GitHub Actions Job Execution)

Started Jul 07, 2025, 08:46 PM UTC· resolved Jul 07, 2025, 10:24 PM UTC

  1. investigating Jul 07, 2025, 08:46 PM UTC

    We are experiencing general degraded performance. We’re working to resolve the problem as quickly as we can. We’ll share another update shortly. A subset of BuildJet for GitHub Actions users are impacted.

  2. investigating Jul 07, 2025, 10:09 PM UTC

    GitHub has now acknowledged their issue on their status page: https://www.githubstatus.com/incidents/djpyjb19cfjd We’re continuing to monitor the situation and exploring mitigations on our end.

  3. resolved Jul 07, 2025, 10:24 PM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor June 17, 2025 Incident with GitHub Actions 19m Current status by service (GitHub Actions Job Execution)

Started Jun 17, 2025, 07:52 PM UTC· resolved Jun 17, 2025, 08:11 PM UTC

  1. investigating Jun 17, 2025, 07:52 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/y7lb2rg4btd7

  2. resolved Jun 17, 2025, 08:11 PM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor June 12, 2025 Incident with GitHub Actions 1h 35m Current status by service (GitHub Actions Job Execution)

Started Jun 12, 2025, 06:54 PM UTC· resolved Jun 12, 2025, 08:29 PM UTC

  1. investigating Jun 12, 2025, 06:54 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/d9xd9k1j6sl0

  2. resolved Jun 12, 2025, 08:29 PM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor June 5, 2025 Incident with GitHub Actions 53m Current status by service (GitHub Actions Job Execution)

Started Jun 05, 2025, 06:39 PM UTC· resolved Jun 05, 2025, 07:32 PM UTC

  1. investigating Jun 05, 2025, 06:39 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/ry1gsyjqj4qh

  2. resolved Jun 05, 2025, 07:32 PM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor June 4, 2025 Incident with GitHub Actions 40m Current status by service (GitHub Actions Job Execution)

Started Jun 04, 2025, 03:19 PM UTC· resolved Jun 04, 2025, 03:59 PM UTC

  1. investigating Jun 04, 2025, 03:19 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/v7vmwf4pyx6y

  2. resolved Jun 04, 2025, 03:59 PM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor May 26, 2025 Incident with GitHub Actions 2h 16m Current status by service (GitHub Actions Job Execution)

Started May 26, 2025, 07:29 AM UTC· resolved May 26, 2025, 09:45 AM UTC

  1. investigating May 26, 2025, 07:29 AM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/d0nm3xcdc5jw

  2. resolved May 26, 2025, 09:45 AM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor May 22, 2025 Incident with GitHub Actions 1h 35m Current status by service (GitHub Actions Job Execution)

Started May 22, 2025, 07:46 AM UTC· resolved May 22, 2025, 09:21 AM UTC

  1. investigating May 22, 2025, 07:46 AM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/cbdzqm5fw0fm

  2. resolved May 22, 2025, 09:21 AM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor May 8, 2025 Incident with GitHub Actions 1h 16m Current status by service (GitHub Actions Job Execution)

Started May 08, 2025, 03:26 PM UTC· resolved May 08, 2025, 04:42 PM UTC

  1. investigating May 08, 2025, 03:26 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/42gtccf6dd98

  2. resolved May 08, 2025, 04:42 PM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor April 30, 2025 Incident with GitHub Actions 42m Current status by service (GitHub Actions Job Execution)

Started Apr 30, 2025, 08:55 PM UTC· resolved Apr 30, 2025, 09:37 PM UTC

  1. investigating Apr 30, 2025, 08:55 PM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/7r0jg1plygfm

  2. resolved Apr 30, 2025, 09:37 PM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor April 28, 2025 Incident with GitHub 2h 59m Current status by service (GitHub Actions Job Execution)

Started Apr 28, 2025, 08:15 AM UTC· resolved Apr 28, 2025, 11:14 AM UTC

  1. investigating Apr 28, 2025, 08:15 AM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/7lbnm9mg6549

  2. resolved Apr 28, 2025, 11:14 AM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor April 23, 2025 Incident with GitHub Actions 26m Current status by service (GitHub Actions Job Execution)

Started Apr 23, 2025, 07:30 AM UTC· resolved Apr 23, 2025, 07:56 AM UTC

  1. investigating Apr 23, 2025, 07:30 AM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/lrby2hyk80dh

  2. resolved Apr 23, 2025, 07:56 AM UTC

    The incident has been resolved by GitHub.

Read the full incident report →

Minor March 21, 2025 Incident with GitHub Actions 1h 8m Current status by service (GitHub Actions Job Execution)

Started Mar 21, 2025, 08:29 AM UTC· resolved Mar 21, 2025, 09:37 AM UTC

  1. investigating Mar 21, 2025, 08:29 AM UTC

    We are experiencing general degraded performance caused by GitHub's incident. Please observe the corresponding GitHub incident updates at https://www.githubstatus.com/incidents/slgf0l5smt3j

  2. resolved Mar 21, 2025, 09:37 AM UTC

    The incident has been resolved by GitHub.

Read the full incident report →