Skip to content

Outage tracker / GitHub / In Singapore

Is GitHub down in Singapore?

Vendor reports no incidentWhat GitHub reports

GitHub reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:28 UTC.

GitHub's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Partially degradedin Singapore, measured from Singapore

Our Singapore probe last checked GitHub at Nov 5, 2026, 3:32 PM UTC and read partially degraded.

Over the last 24 hours we completed 355 checks from Singapore and 355 answered cleanly, 100.00% availability.

Of the 9 other regions we check GitHub from, 6 read partially degraded and 3 read checks passing right now.

Email me when GitHub reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is GitHub's own statement from its status page, with our regional reading beside it.

What our Singapore probe measured

SingaporePartially degraded355 checks in 24h, 100.00%

Last checked Nov 5, 2026, 3:32 PM UTC.

GitHub from Singapore over the last 30 days

Over the last 30 days, GitHub answered our Singapore probe in 911 ms on average, and 1 check in 20 took longer than 1,578 ms.

Ranked by average response time across the 10 cities we check GitHub from, Singapore 10th; London was fastest at 444 ms and Singapore slowest at 911 ms.

From Singapore we ran 10,634 checks of GitHub in 30 days, and 10,628 answered cleanly: 99.94% availability.

3 of the 30 days had at least one failed check. The weakest was Oct 25 (UTC), at 99.16% across 360 checks.

In Singapore local time (GMT+8), GitHub was slowest around 6 AM, at 1,288 ms on average over the last 14 days, and quickest around 5 AM, at 1,029 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5221100.00%905 ms
Wed, Nov 4358100.00%933 ms
Tue, Nov 3353100.00%942 ms
Mon, Nov 2358100.00%979 ms
Sun, Nov 1358100.00%1,102 ms
Sat, Oct 31359100.00%1,053 ms
Fri, Oct 30361100.00%1,162 ms
Thu, Oct 29358100.00%1,221 ms
Wed, Oct 28358100.00%1,213 ms
Tue, Oct 27358100.00%1,176 ms
Mon, Oct 2636099.44%1,103 ms
Sun, Oct 2536099.16%1,393 ms
Sat, Oct 2436099.72%1,192 ms
Fri, Oct 23362100.00%1,223 ms

GitHub outages measured from Singapore

Our Singapore probe measured no confirmed GitHub outage in the last 90 days.

How the other regions read right now

Of the 9 other regions we check GitHub from, 6 read partially degraded and 3 read checks passing right now.

Probe cityRight nowLast 24h
AshburnPartially degraded100.00% of 606 checks
San JosePartially degraded100.00% of 430 checks
FrankfurtChecks passing100.00% of 392 checks
TokyoPartially degraded100.00% of 244 checks
ChicagoChecks passing99.72% of 358 checks
TorontoPartially degraded100.00% of 358 checks
LondonPartially degraded100.00% of 355 checks
SydneyPartially degraded100.00% of 355 checks
São PauloChecks passing99.72% of 358 checks

Other countries we check GitHub from

How we measured this

Singapore readings on this page come from RealUptime's own Singapore probe against GitHub's public endpoints. They are not user reports, and they are not GitHub's own status page.

See GitHub's full check readings, the 90-day history by region, or the outage tracker methodology.

Check your own site from Singapore

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter