← HonkWatch.com

Is GitHub down in Cocos (Keeling) Islands?

No problems reported with GitHub right now

People in Cocos (Keeling) Islands: 0 reports in the last hour Official page: No incident reported, checked 1 min ago Our checks: loads from 35 of 35 places

API (API Requests): Operational

GitHub reports no current incident. Updated 7 Nov, 19:30 UTC, 1 min ago · Official status page
Report a problem
Change country

Known issues (from GitHub's status page)

GitHub's status page lists no open incident and no planned maintenance.

In GitHub's own words, as we read them every 2.5 minutes, last 1 min ago. Read GitHub's status page

Reports from people in Cocos (Keeling) Islands

Last 24 hours · Cocos (Keeling) Islands · times in UTC

0 reports

No community reports in the last 24 hours from Cocos (Keeling) Islands. Having trouble? Add your report.

024 00:0006:0012:0018:00 19:45-19:50 UTC: 30 of 30 places loaded it, typical 87 ms19:50-19:55 UTC: 22 of 22 places loaded it, typical 108 ms19:55-20:00 UTC: 23 of 23 places loaded it, typical 48 ms20:00-20:05 UTC: 25 of 25 places loaded it, typical 114 ms20:05-20:10 UTC: 23 of 23 places loaded it, typical 96 ms20:10-21:00 UTC: 35 of 35 places loaded it, typical 69 to 99 ms21:00-21:05 UTC: 21 of 21 places loaded it, typical 80 ms21:05-21:10 UTC: 26 of 26 places loaded it, typical 77 ms21:10-21:25 UTC: 35 of 35 places loaded it, typical 75 to 81 ms21:25-21:30 UTC: 25 of 25 places loaded it, typical 77 ms21:30-21:45 UTC: 35 of 35 places loaded it, typical 77 to 81 ms21:45-21:50 UTC: 34 of 34 places loaded it, typical 86 ms21:50-21:55 UTC: 23 of 23 places loaded it, typical 90 ms21:55-22:05 UTC: 35 of 35 places loaded it, typical 87 to 90 ms22:05-22:10 UTC: 28 of 28 places loaded it, typical 85 ms22:10-09:15 UTC: 35 of 35 places loaded it, typical 60 to 97 ms09:15-09:20 UTC: 33 of 33 places loaded it, typical 84 ms09:20-19:30 UTC: 35 of 35 places loaded it, typical 57 to 85 ms19:30-19:35 UTC: 2 of 2 places loaded it Typical response time of the places that loaded it, at most 114 ms

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

Strip under the bars: how many places loaded github.com in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Our checks are worldwide; the bars count reports from Cocos (Keeling) Islands only.

Latest checks, 19:30-19:35 UTC: 2 of 2 places loaded it.

Report totals as of 7 Nov, 19:31 UTC

Report a problem with GitHub

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Cocos (Keeling) Islands

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 Cocos (Keeling) Islands. The report chart above is filtered to Cocos (Keeling) Islands.

Our own checks of github.com

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Mumbai: loaded in 110 ms Port Louis: loaded in 221 ms Seattle: loaded in 27 ms Melbourne: loaded in 68 ms Cape Town: loaded in 122 ms Sydney: loaded in 74 ms Warsaw: loaded in 77 ms Jakarta: loaded in 76 ms São Paulo: loaded in 28 ms St. Louis: loaded in 231 ms Los Angeles: loaded in 287 ms Seoul: loaded in 29 ms Dallas: loaded in 164 ms New York: loaded in 38 ms Hong Kong: loaded in 142 ms Singapore: loaded in 20 ms Lauterbourg: loaded in 57 ms Querétaro: loaded in 233 ms Hamina: loaded in 166 ms Bangalore: loaded in 104 ms Johannesburg: loaded in 24 ms Doha: loaded in 198 ms Amsterdam: loaded in 36 ms Portsmouth: loaded in 27 ms Osaka: loaded in 43 ms New Jersey: loaded in 51 ms Frankfurt: loaded in 10 ms Tel Aviv: loaded in 528 ms Madrid: loaded in 124 ms Atlanta: loaded in 75 ms Toronto: loaded in 100 ms Santiago: loaded in 206 ms Tokyo: loaded in 32 ms London: loaded in 19 ms Delhi: loaded in 116 ms
  • MumbaiReachable110 ms, just now
  • Port LouisReachable221 ms, just now
  • SeattleReachable27 ms, 3 min ago
  • MelbourneReachable68 ms, 3 min ago
  • Cape TownReachable122 ms, 3 min ago
  • SydneyReachable74 ms, 3 min ago
  • WarsawReachable77 ms, 3 min ago
  • JakartaReachable76 ms, 3 min ago
  • São PauloReachable28 ms, 4 min ago
  • St. LouisReachable231 ms, 4 min ago
  • Los AngelesReachable287 ms, 4 min ago
  • SeoulReachable29 ms, 4 min ago
  • DallasReachable164 ms, 4 min ago
  • New YorkReachable38 ms, 4 min ago
  • Hong KongReachable142 ms, 4 min ago
  • SingaporeReachable20 ms, 4 min ago
  • LauterbourgReachable57 ms, 4 min ago
  • QuerétaroReachable233 ms, 4 min ago
  • HaminaReachable166 ms, 4 min ago
  • BangaloreReachable104 ms, 4 min ago
  • JohannesburgReachable24 ms, 4 min ago
  • DohaReachable198 ms, 4 min ago
  • AmsterdamReachable36 ms, 4 min ago
  • PortsmouthReachable27 ms, 4 min ago
  • OsakaReachable43 ms, 4 min ago
  • New JerseyReachable51 ms, 4 min ago
  • FrankfurtReachable10 ms, 4 min ago
  • Tel AvivReachable528 ms, 4 min ago
  • MadridReachable124 ms, 5 min ago
  • AtlantaReachable75 ms, 5 min ago
  • TorontoReachable100 ms, 5 min ago
  • SantiagoReachable206 ms, 5 min ago
  • TokyoReachable32 ms, 5 min ago
  • LondonReachable19 ms, 5 min ago
  • DelhiReachable116 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

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:37 UTC, partial outage for 46 min (Open incident: Degraded performance for multiple GitHub services).

Last 9030 days

92.84% 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 84 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

Recent problems

5 Nov, 23:37 UTCPartial outage46 minOpen incident: Degraded performance for multiple GitHub services
5 Nov, 16:51 UTCPartial outage53 minOpen incident: Incident with Actions
4 Nov, 17:42 UTCPartial outage36 minOpen incident: Incident with Actions
4 Nov, 16:07 UTCPartial outage55 minOpen incident: Incident with Actions and Pages
4 Nov, 08:48 UTCPartial outage3 h 4 minOpen incident: Incident with Pull Requests, Git Operations and Issues
3 Nov, 21:00 UTCPartial outage1 h 45 minOpen incident: Incident with Git Operations
3 Nov, 13:26 UTCPartial outage32 minOpen incident: Incident with API, Git, and Copilot requests
2 Nov, 17:49 UTCPartial outage39 minOpen incident: Elevated errors on GPT-5.4 Nano
What can I try?

Having trouble with GitHub?

  1. Compare reports from Cocos (Keeling) Islands 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 down, or is it just me?

The GitHub 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 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.

Other services in Developer tools

Each card shows that service's own status, not GitHub's. A problem listed here does not mean GitHub has one.

See the live outage feed for Cocos (Keeling) Islands · Find another service