We started checking SourceHut on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when SourceHut reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what SourceHut's own status page declared. Below it, any public chatter we saw about SourceHut and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what SourceHut's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about SourceHut in the last 24 hours, which is not evidence that nothing is wrong.
SourceHut's status page
git.sr.ht under high load: minor incident
git.sr.ht under high load: minor incident, from 15:00 UTC to now, still open per their page.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is SourceHut's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention SourceHut next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
Confirmation probe15:41 UTC, US-West: a new incident on their status page prompted an extra probe. Result: SourceHut answered normally.
Confirmation probe15:40 UTC, Europe: a new incident on their status page prompted an extra probe. Result: SourceHut answered normally.
Confirmation probe15:40 UTC, Asia-Pacific: a new incident on their status page prompted an extra probe. Result: SourceHut answered normally.
Confirmation probe15:40 UTC, US-East: a new incident on their status page prompted an extra probe. Result: SourceHut answered normally.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
99.32%
443
US-West
99.41%
341
Europe
99.68%
311
Asia-Pacific
98.95%
190
Their declared record
SourceHut's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
git.sr.ht under high loadOngoing, minor incident
Nov 5, 2026, 3:00 PM UTC, open for 2h 20m so far
their latest update (Nov 5, 2026, 3:00 PM 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.
Planned maintenance on all services cancelled!Maintenance
Oct 19, 2026, 11:00 AM UTC to Oct 19, 2026, 11:00 AM UTC (0 min)completed
their latest update (Oct 19, 2026, 11:00 AM UTC): Planned maintenance on October 19th will cause intermittent outages : Planned maintenance starting at 11:00 UTC will affect all services, causing intermittent outages that are expected to last between 15 and 30 minutes each. Notably, chat.sr.ht will be rebooted, causing everyone …
SourceHut disrupted by LLM crawlersMinor incident
Jun 6, 2026, 7:00 PM UTC to Sep 14, 2026, 12:00 AM UTC (99d 5h)resolved
their latest update (Sep 14, 2026, 12:00 AM UTC): git.sr.ht is being disrupted by aggressive LLM crawlers . An aggressive botnet is scraping git.sr.ht to obtain data to train large language models. It has been able to circumvent the defenses we ordinarily deploy to mitigate these botnets, and as a consequence git.sr.ht is unstab…
Apr 27, 2026, 5:00 AM UTC to Apr 27, 2026, 5:00 AM UTC (0 min)resolved
their latest update (Apr 27, 2026, 5:00 AM UTC): A phishing campaign is targetting SourceHut users, impersonating SourceHut founder Drew DeVault and stating that SourceHut plans to be shut down following the DDoS attacks which have been affecting service recently. These emails are not authentic. Emails sent by SourceHut are sen…
SourceHut disrupted due to DDoS attackMinor incident
Apr 22, 2026, 3:30 PM UTC to May 20, 2026, 12:00 AM UTC (27d 8h)resolved
their latest update (May 20, 2026, 12:00 AM UTC): SourceHut is being disrupted by a DDoS attack . A DDoS attack similar to the one experienced a couple of weeks ago is currently targetting meta.sr.ht. Many services depend on meta.sr.ht and are therefore also affected. We are looking into mitigations. (15:30 UTC — Apr 22) Migitat…
SourceHut disrupted due to DDoS attackMinor incident
Apr 5, 2026, 10:00 AM UTC to Apr 20, 2026, 12:00 AM UTC (14d 14h)resolved
their latest update (Apr 20, 2026, 12:00 AM UTC): SourceHut was disrupted by a DDoS attack . Over the holidays SourceHut experienced a DDoS attack primarily targetting git.sr.ht. For a period of several hours we experienced severe performance issues and intermittent outages as a result, primarily affecting git.sr.ht. Our upstrea…
git.sr.ht disrupted by LLM crawler botnetsMinor incident
Dec 24, 2025, 1:00 PM UTC to Dec 30, 2025, 1:00 PM UTC (6d 0h)resolved
their latest update (Dec 30, 2025, 1:00 PM UTC): git.sr.ht is experiencing issues due to a crawler botnet. A crawler botnet is aggressively scraping git.sr.ht for content to train large language models and is able to circumvent our usual defenses deployed to prevent them from doing so, and as a result is causing severe performa…
Planned maintenance on all servicesMaintenance
Oct 22, 2025, 11:00 AM UTC to Oct 22, 2025, 12:25 PM UTC (1h 25m)completed
their latest update (Oct 22, 2025, 12:25 PM UTC): The maintenance is complete . All services are operational again. Note that some chat.sr.ht upstream connections may take a while to be re-established due to rate limits. (12:25 UTC — Oct 22) The maintenance window is now open . Disruptions will occur across all services. (11:00 …
Planned maintenance on all servicesMaintenance
Jul 22, 2025, 9:00 AM UTC to Jul 22, 2025, 10:15 AM UTC (1h 15m)completed
their latest update (Jul 22, 2025, 10:15 AM UTC): The maintenance is complete . All services are restored. (10:15 UTC — Jul 22) The maintenance window is now open . Disruptions will occur across all services. (09:00 UTC — Jul 22) Planned maintenance on July 22nd will cause intermittent outages : Planned maintenance starting at 0…
Planned bouncer ugrade on ThursdayMinor incident
Apr 3, 2025, 12:00 PM UTC to Apr 3, 2025, 12:05 PM UTC (5 min)resolved
their latest update (Apr 3, 2025, 12:05 PM UTC): Restart completed . Again, note that some upstream connections may take a while to be re-established due to rate limits. (12:05 UTC — Apr 3) Planned bouncer upgrade is scheduled for Thursday, April 3rd . On Thursday at 12:00 UTC we will be rolling out an upstream update for soju,…
Showing the 10 most recent of 63 incidents SourceHut has declared in the history we hold.
These entries are SourceHut's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
SourceHut's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.