sourcehut
/
sourcehut.org
mirror of https://git.sr.ht/~sircmpwn/sourcehut.org
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add details regarding ongoing outage 

Hopefully this will trigger a build to be submitted and it will be
published on pages automatically... assuming we have enough infra online
and it's configured correctly.
This commit is contained in:
Drew DeVault 2024-01-16 19:22:47 +01:00
parent 4ea3c80a9b
commit b1d43f76d3
2 changed files with 115 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
assets/main.scss
View File

@ -91,6 +91,10 @@ img, video {
color: #2bb34b;
}
.text-warning {
color: darken(#ffc107, 10);
}
.text-danger {
color: #ff3e3e;
}
@ -368,6 +372,11 @@ header {
}
h1 {
// XXX TEMP
border: 1px solid darken(#f1aeb5, 10) !important;
background: darken(#f8d7da, 20) !important;
// END TEMP
padding: 0.25rem 1rem;
margin: 0 -1rem 0.5rem -1rem;
background: rgba(255, 255, 255, 1.0);

106
content/blog/2024-01-16-SourceHut-outage.md Normal file
View File

@ -0,0 +1,106 @@
---
title: Information regarding the SourceHut outage
author: Drew DeVault
date: 2024-01-16
---
SourceHut is currently experiencing an extended outage due to a distributed
denial-of-service (DDoS) attack. We have been hard at work restoring service to
our users, and expect the remaining services to come online this week. Thank you
for your patience and words of support, we appreciate it very much.
Once we have finished handling the majority of the work associated with the
outage mitigations, we will be publishing a full post-mortem. For up-to-date
information regarding the status of the outage and work associated with it,
please consult [status.sr.ht](https://status.sr.ht).
The billing system has been disabled for the duration of the outage: you will
not be charged until we have fully restored service. Once restored, we will
credit paid users with service for the duration of the outage.
The current service status is as follows:
<table>
<thead>
<tr>
<th>Service</th>
<th style="min-width: 300px">Status</th>
</tr>
</thead>
<tbody>
<tr>
<td>sr.ht (project hub)</td>
<td class="text-success">Full service</td>
</tr>
<tr>
<td>meta.sr.ht</td>
<td class="text-success">Full service</td>
</tr>
<tr>
<td>git.sr.ht</td>
<td><span class="text-success">Full service</span><sup>1</sup></td>
</tr>
<tr>
<td>hg.sr.ht</td>
<td><span class="text-success">Full service</span><sup>1</sup></td>
</tr>
<tr>
<td>lists.sr.ht</td>
<td class="text-success">Full service</td>
</tr>
<tr>
<td>todo.sr.ht</td>
<td class="text-success">Full service</td>
</tr>
<tr>
<td>man.sr.ht</td>
<td class="text-success">Full service</td>
</tr>
<tr>
<td>paste.sr.ht</td>
<td class="text-success">Full service</td>
</tr>
<tr>
<td>builds.sr.ht</td>
<td><span class="text-success">Full service</span><sup>3</sup></td>
</tr>
<tr>
<td>chat.sr.ht</td>
<td class="text-danger">Out of service</td>
</tr>
<tr>
<td>pages.sr.ht</td>
<td><span class="text-warning">Degraded service</span><sup>2</sup></td>
</tr>
</tbody>
</table>
<sup>1</sup> We have restored git and hg from backups which were several hours
old at the time the outage began, and manually imported changes which took place
between the time of the last backup and the start of the outage.
If your repository is still out-of-date, please take the following steps:
1. If you have access to the up-to-date repository locally, please `git push` or
`hg push` your changes to bring the online version up-to-date.
2. If you do not have access to your repository locally, please
[contact support](mailto:~sircmpwn/sr.ht-support@lists.sr.ht) for assistance.
<sup>2</sup> pages.sr.ht is online for full service, with the following
caveats:
1. Publish operations are working with degraded performance
2. Manual intervention is required for users using custom domains with apex
records (e.g. example.org rather than subdomain.example.org)
For users with apex records, please update your apex record as follows:
@ IN A 141.95.4.185
This IP address is available on a temporary basis. Make sure your email address
on file is up-to-date; we will email you if and when it changes to notify you
of the steps required to update your website.
<sup>3</sup> builds is currently running at half of its planned capacity. We are
working on bringing it up to full capacity by tomorrow morning, but in the
meanwhile you may experience longer queue times for your build jobs.