Skip to content

Outage tracker / SourceHut / In Japan

Is SourceHut down in Japan?

Vendor reports an incidentWhat SourceHut reports

SourceHut reports an incident on its status page: git.sr.ht under high load.

Impact: minor. Since 2026-11-05 15:00 UTC.

Latest update, 2026-11-05 15:00 UTC: Excessive load on git.sr.ht causes intermittent outages : git.sr.ht is currently under very high load, to the point of occasional service disruptions. It seems to be caused by cooccurrence of a variety of external factors. We are working on mitigations.

SourceHut'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.

Checks passingin Japan, measured from Tokyo

Our Tokyo probe last checked SourceHut at Nov 6, 2026, 5:27 PM UTC and read checks passing.

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

Of the 3 other regions we check SourceHut from, all 3 read checks passing right now.

Email me when SourceHut 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 SourceHut's own statement from its status page, with our regional reading beside it.

What our Tokyo probe measured

TokyoChecks passing58 checks in 24h, 100.00%

Last checked Nov 6, 2026, 5:27 PM UTC.

SourceHut from Tokyo over the last 30 days

Over the last 30 days, SourceHut answered our Tokyo probe in 2,102 ms on average, and 1 check in 20 took longer than 2,916 ms.

Ranked by average response time across the 4 cities we check SourceHut from, Tokyo 4th; Frankfurt was fastest at 550 ms and Tokyo slowest at 2,102 ms.

From Tokyo we ran 249 checks of SourceHut in 5 days, and 247 answered cleanly: 99.19% availability.

2 of the 5 days had at least one failed check. The weakest was Nov 2 (UTC), at 96.29% across 27 checks.

In Tokyo local time (GMT+9), SourceHut was slowest around 6 PM, at 3,056 ms on average over the last 14 days, and quickest around 3 PM, at 1,578 ms.

Day (UTC)ChecksAvailabilityAverage response
Fri, Nov 643100.00%2,069 ms
Thu, Nov 560100.00%2,272 ms
Wed, Nov 46098.33%2,120 ms
Tue, Nov 359100.00%1,986 ms
Mon, Nov 22796.29%1,994 ms

SourceHut outages measured from Japan

Our Tokyo probe measured no confirmed SourceHut outage in the last 90 days.

How the other regions read right now

Of the 3 other regions we check SourceHut from, all 3 read checks passing right now.

Probe cityRight nowLast 24h
AshburnChecks passing100.00% of 143 checks
San JoseChecks passing100.00% of 110 checks
FrankfurtChecks passing100.00% of 98 checks

Other countries we check SourceHut from

How we measured this

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

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

Japan readings here are taken from that country and show the time of the last one, but SourceHut has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Tokyo

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