by HonkWatch

Is GitHub Actions down in Libya?

No problems reported with GitHub Actions right now

Libya No reports in the last hour checked 3 min ago
GitHub Actions reports no current incident. Updated 6 Nov, 23:44 UTC, 3 min ago · Official status page
Report a problemFollow community reports
Change country

Reports from people in Libya

Last 24 hours · Libya · times in UTC

0 reports

No community reports in the last 24 hours from Libya. Having trouble? Add your report.

024 00:0006:0012:0018:0000:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 6 Nov, 23:47 UTC

Report a problem with GitHub Actions

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in Libya

Monitor the provider status with HonkWatch

Get monitoring alerts for GitHub Actions

HonkWatch watches the GitHub Actions status page for you and alerts you by email, Slack, Discord or Telegram when it reports a problem.

Free account required. GitHub Actions is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

Where this status comes from

Provider updates and website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Libya. The report chart above is filtered to Libya.

Our own checks of github.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Portsmouth: loaded in 40 ms New Jersey: loaded in 81 ms Tel Aviv: loaded in 21 ms Frankfurt: loaded in 12 ms Atlanta: loaded in 68 ms Madrid: loaded in 110 ms Toronto: loaded in 102 ms Tokyo: loaded in 28 ms Santiago: loaded in 208 ms London: loaded in 17 ms Delhi: loaded in 130 ms Mumbai: loaded in 40 ms Port Louis: loaded in 182 ms Melbourne: loaded in 70 ms Seattle: loaded in 25 ms Sydney: loaded in 28 ms Cape Town: loaded in 128 ms Warsaw: loaded in 77 ms St. Louis: loaded in 120 ms Jakarta: loaded in 76 ms São Paulo: loaded in 29 ms Los Angeles: loaded in 288 ms Seoul: loaded in 21 ms New York: loaded in 37 ms Dallas: loaded in 164 ms Hong Kong: loaded in 150 ms Singapore: loaded in 20 ms Lauterbourg: loaded in 60 ms Querétaro: loaded in 230 ms Hamina: loaded in 164 ms Bangalore: loaded in 94 ms Johannesburg: loaded in 20 ms Doha: loaded in 200 ms Amsterdam: loaded in 35 ms Osaka: loaded in 38 ms
  • PortsmouthReachable40 ms, just now
  • New JerseyReachable81 ms, just now
  • Tel AvivReachable21 ms, just now
  • FrankfurtReachable12 ms, just now
  • AtlantaReachable68 ms, just now
  • MadridReachable110 ms, just now
  • TorontoReachable102 ms, just now
  • TokyoReachable28 ms, just now
  • SantiagoReachable208 ms, just now
  • LondonReachable17 ms, just now
  • DelhiReachable130 ms, just now
  • MumbaiReachable40 ms, just now
  • Port LouisReachable182 ms, just now
  • MelbourneReachable70 ms, 4 min ago
  • SeattleReachable25 ms, 4 min ago
  • SydneyReachable28 ms, 4 min ago
  • Cape TownReachable128 ms, 4 min ago
  • WarsawReachable77 ms, 4 min ago
  • St. LouisReachable120 ms, 4 min ago
  • JakartaReachable76 ms, 4 min ago
  • São PauloReachable29 ms, 4 min ago
  • Los AngelesReachable288 ms, 4 min ago
  • SeoulReachable21 ms, 4 min ago
  • New YorkReachable37 ms, 4 min ago
  • DallasReachable164 ms, 4 min ago
  • Hong KongReachable150 ms, 4 min ago
  • SingaporeReachable20 ms, 4 min ago
  • LauterbourgReachable60 ms, 5 min ago
  • QuerétaroReachable230 ms, 5 min ago
  • HaminaReachable164 ms, 5 min ago
  • BangaloreReachable94 ms, 5 min ago
  • JohannesburgReachable20 ms, 5 min ago
  • DohaReachable200 ms, 5 min ago
  • AmsterdamReachable35 ms, 5 min ago
  • OsakaReachable38 ms, 5 min ago

This is separate from the status page: we request github.com and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of GitHub Actions

GitHub
  • Git OperationsOperational
  • WebhooksOperational
  • Visit www.githubstatus.com for more informationOperational
  • API RequestsOperational
  • IssuesOperational
  • Pull RequestsOperational
  • ActionsOperational
  • PackagesOperational
  • PagesOperational
  • CopilotOperational
  • CodespacesOperational
  • Copilot AI Model ProvidersOperational

Incidents and maintenance

No open incidents or planned maintenance.

Outage history

Last problem: 5 Nov, 23:39 UTC, partial outage for 43 min (Open incident: Degraded performance for multiple GitHub services).

Last 9030 days

91.57% of the time without a reported outage, since 2 Nov

Of the last 90 days, 5 had a partial or major outage, 0 had maintenance only and 85 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of github.com that failed (9,342 checks). Shaded: when GitHub Actions's status page reported a problem. Community reports appear separately above, alongside our checks and provider updates.

0%5%10% 00:0006:0012:0018:0000:00 0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 104 checks failed0% of 106 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 99 checks failed0% of 111 checks failed0% of 88 checks failed0% of 103 checks failed0% of 101 checks failed0% of 105 checks failed0% of 97 checks failed0% of 79 checks failed0% of 80 checks failed0% of 109 checks failed0% of 91 checks failed0% of 108 checks failed0% of 99 checks failed0% of 94 checks failed0% of 79 checks failed0% of 87 checks failed0% of 95 checks failed0% of 103 checks failed0% of 83 checks failed0% of 84 checks failed0% of 84 checks failed0% of 88 checks failed0% of 92 checks failed0% of 79 checks failed0% of 79 checks failed0% of 87 checks failed0% of 81 checks failed0% of 79 checks failed0% of 86 checks failed0% of 74 checks failed0% of 71 checks failed0% of 90 checks failed0% of 89 checks failed0% of 106 checks failed0% of 89 checks failed0% of 85 checks failed0% of 103 checks failed0% of 104 checks failed0% of 98 checks failed0% of 74 checks failed0% of 85 checks failed0% of 96 checks failed0% of 84 checks failed0% of 103 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 89 checks failed0% of 95 checks failed0% of 106 checks failed0% of 103 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 105 checks failed0% of 13 checks failed

Recent problems

5 Nov, 23:39 UTCPartial outage43 minOpen incident: Degraded performance for multiple GitHub services
5 Nov, 16:53 UTCPartial outage50 minOpen incident: Incident with Actions
4 Nov, 17:41 UTCPartial outage36 minOpen incident: Incident with Actions
4 Nov, 16:06 UTCPartial outage58 minOpen incident: Incident with Actions and Pages
4 Nov, 08:47 UTCPartial outage3 h 4 minOpen incident: Incident with Pull Requests, Git Operations and Issues
3 Nov, 21:00 UTCPartial outage1 h 44 minOpen incident: Incident with Git Operations
3 Nov, 13:29 UTCPartial outage32 minOpen incident: Incident with API, Git, and Copilot requests
2 Nov, 17:48 UTCPartial outage39 minOpen incident: Elevated errors on GPT-5.4 Nano
What can I try?

Having trouble with GitHub Actions?

  1. Compare reports from Libya and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is GitHub Actions down, or is it just me?

The GitHub Actions status page reports no problem and our own checks reach github.com. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

How do we know?

We read the official GitHub Actions status page and load github.com from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The status page every 2.5 minutes, day and night, and the website every 5 minutes. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

More in CI/CD

See the live outage feed for Libya · Find another service