Planned maintenance is complete. There may be some residual issues. (18:00 UTC — Mar 11)
Planned maintenance is underway (16:00 UTC — Mar 11)
Planned maintenance on March 11th will cause intermittent outages: Planned maintenance will affect all services, causing intermittent outages that are expected to last between 15 and 30 minutes. (19:00 UTC — Mar 5)
Maintenance complete Service has been restored. (16:30 UTC — Jan 8)
Maintenance has begun: This maintenance is now underway. (16:00 UTC — Jan 8)
Planned maintenance on January 8th will cause a total service outage: We have scheduled maintenance for next Wednesday at 16:00 UTC to perform normal database maintenance. We expect a total outage of all services which should last no more than 2 hours. (16:00 UTC — Jan 8)
A planned upgrade hit unexpected errors: We are working on a solution. (19:00 UTC — Dec 22)
Migration complete pending DNS propegation: The migration is completed and all service is restored. However, you may not see service restored until your DNS provider finishes processing the updates. (17:45 UTC — Dec 20)
git.sr.ht is now read-only: We’re in the thick of the migration now. Write access should be restored within an hour. (17:30 UTC — Dec 20)
Planned upgrades to git.sr.ht will impact availability: We are planning on moving git.sr.ht to a new server today. The service may be read-only at times during this process. (14:30 UTC — Dec 20)
Deployments complete: The deployment has been completed for all services and no issues have been found. Service should be operating normally. (15:45 UTC — Nov 30)
Ongoing deployment causing service disruption: We are currently deploying a major change in the Sourcehut architecture, which is likely to cause intermittent outages during deployment as services are rotated onto the new system and oversights are discovered and resolved. (15:00 UTC — Nov 30)
Service restored: Service has been restored. I/O exhaustion flipped git.sr.ht’s filesystem into read-only mode and on reboot, filesystem corruption was found. The integrity of user data was not affected, and if they were, the integrity of our backups was found to be correct in an emergency integrity test (routine checks are also performed regularly and found to be in order).
An investigation into the underlying causes of the failure is ongoing. (20:08 UTC — Nov 15)
Resolved The issue has been fixed. It may take time for DNS updates to propegate to your local server. (21:45 UTC — Sep 29)
Working on the issue We have reached support and they’ve rolled back the changes. We’re monitoring our services to make sure the trasition occurs smoothly. (21:00 UTC — Sep 29)
No response We are still waiting for an update from our registrar. (20:00 UTC — Sep 29)
Major DNS outage: While deploying IPv6 support across Sourcehut, we submitted a routine request to our domain registrar to add IPv6 glue records for our nameservers. In the course of doing this, the registrar also removed the IPv4 glue records. We are attempting to reach them for assistance. Services are severely disrupted in the meantime. (10:00 UTC — Sep 29)
Maintenance complete: The planned maintenance is complete. Write access should become available once your DNS cache is flushed. The TTL is 1 hour. (15:34 UTC — Jun 12)
Planned maintenance: git.sr.ht is currently read-only as we complete planned maintenance on the service. (15:00 UTC — Jun 12)
Upcoming planned maintenance: We have an upcoming planned database outage on May 10th. This will cause a temporary service disruption for all sr.ht services. The outage is expected to last less than 2 hours. (12:00 UTC — May 10)
Maintenance complete: Everything appears to be in good working order. (20:00 UTC — Feb 18)
Upcoming planned maintenance: We’re doing planned maintenance on Monday that will cause sporadic outages throughout the day as our hosts are moved into a larger rack. In exchange for your patience, we’ll be installing a much more powerful host for builds.sr.ht builds at the same time. (12:00 UTC — Feb 18)