Is SourceHut down in the US?
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.
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 the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked SourceHut at Nov 5, 2026, 4:11 PM UTC.
Over the last 24 hours we completed 253 checks from Ashburn and San Jose and 252 answered cleanly, 99.60% availability.
Of the 2 other regions we check SourceHut from, all 2 read checks passing right now.
Email me when SourceHut reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 4:11 PM UTC.
SourceHut from Ashburn and San Jose over the last 30 days
Over the last 30 days, SourceHut answered our Ashburn probe in 1,057 ms on average, and 1 check in 20 took longer than 1,591 ms.
Over the last 30 days, SourceHut answered our San Jose probe in 1,412 ms on average, and 1 check in 20 took longer than 2,137 ms.
Ranked by average response time across the 4 cities we check SourceHut from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 569 ms and Tokyo slowest at 2,057 ms.
From Ashburn and San Jose we ran 773 checks of SourceHut in 4 days, and 768 answered cleanly: 99.35% availability.
3 of the 4 days had at least one failed check. The weakest was Nov 4 (UTC), at 98.80% across 251 checks.
In Ashburn local time (EST), SourceHut was slowest around 3 AM, at 1,477 ms on average over the last 14 days, and quickest around 4 PM, at 773 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 171 | 99.41% | 1,309 ms |
| Wed, Nov 4 | 251 | 98.80% | 1,155 ms |
| Tue, Nov 3 | 247 | 99.59% | 1,252 ms |
| Mon, Nov 2 | 104 | 100.00% | 1,098 ms |
SourceHut outages measured from the US
Our Ashburn and San Jose probes measured no confirmed SourceHut outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check SourceHut from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 98.98% of 99 checks |
| Tokyo | Checks passing | 100.00% of 60 checks |
Other countries we check SourceHut from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes 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.
The US 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 Ashburn
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 serversRun 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