Ιστορικό διακοπών του Readme

1. 23 Οκτωβρίου 2026 στις 3:46 μ.μ. UTCinvestigating

   Αυτή τη στιγμή ερευνούμε ένα θέμα που προκαλεί αυξημένα 503 λάθη και χρονόμετρα κατά τη φόρτωση σελίδων τεκμηρίωσης.

2. 23 Οκτωβρίου 2026 στις 3:46 μ.μ. UTCinvestigating

   Συνεχίζουμε να ερευνούμε αυτό το ζήτημα.

3. 23 Οκτωβρίου 2026 στις 3:47 μ.μ. UTCidentified

   Το θέμα έχει εντοπιστεί και υλοποιείται μια λύση.

4. 23 Οκτωβρίου 2026 στις 4:07 μ.μ. UTCmonitoring

   Εφαρμόστηκε μια ρύθμιση και παρακολουθούμε τα αποτελέσματα.

5. 23 Οκτωβρίου 2026 στις 4:09 μ.μ. UTCresolved

   Το περιστατικό λύθηκε.

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 14 Οκτωβρίου 2026 στις 10:44 μ.μ. UTCinvestigating

   Ερευνούμε γιατί οι σελίδες δείχνουν 404

2. 14 Οκτωβρίου 2026 στις 10:51 μ.μ. UTCidentified

   Εντοπίσαμε το θέμα και εργαζόμαστε πάνω σε ένα σημείο

3. 14 Οκτωβρίου 2026 στις 10:52 μ.μ. UTCmonitoring

   Η επισκευή έχει αναπτυχθεί και αυτή τη στιγμή αναπτύσσουμε τους επιχειρησιακούς διακομιστές. Μπορεί να υπάρχουν κάποια λανθάνοντα 404s, γι 'αυτό παρακαλώ ενημερώστε την υποστήριξη αν είστε ακόμα τρέχει σε θέματα

4. 14 Οκτωβρίου 2026 στις 10:55 μ.μ. UTCresolved

   Τα σχέδια θα πρέπει να εμφανίζονται ξανά. Παρακαλώ επικοινωνήστε με το [email protected] αν εξακολουθείτε να συναντάτε 404 λάθη.

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 22 Σεπτεμβρίου 2026 στις 2:22 μ.μ. UTCinvestigating

   Αυτή τη στιγμή ερευνούμε αυξημένη λανθάνουσα συχνότητα και αργούς χρόνους απόκρισης που επηρεάζουν κόμβους. Ενεργά εργάζονται για την αναγνώριση της βασικής αιτίας και την αποκατάσταση της κανονικής υπηρεσίας.

2. 22 Σεπτεμβρίου 2026 στις 2:41 μ.μ. UTCmonitoring

   Εφαρμόστηκε μια διόρθωση και παρακολουθούμε τα αποτελέσματα. Οι επιδόσεις πρέπει να επιστρέφουν στο φυσιολογικό.

3. 22 Σεπτεμβρίου 2026 στις 3:03 μ.μ. UTCmonitoring

   Έχουμε εντοπίσει πρόσθετους παράγοντες που συμβάλλουν και εργαζόμαστε ενεργά για να τους διορθώσουμε.

4. 22 Σεπτεμβρίου 2026 στις 3:16 μ.μ. UTCmonitoring

   Συνεχίζουμε να παρακολουθούμε για τυχόν περαιτέρω ζητήματα.

5. 22 Σεπτεμβρίου 2026 στις 4:44 μ.μ. UTCresolved

   Το περιστατικό λύθηκε.

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 8 Σεπτεμβρίου 2026 στις 4:04 μ.μ. UTCinvestigating

   Η διεύθυνσή μας βιώνει μια διακοπή. Η ικανότητα των τελικών χρηστών να επισκέπτονται το κέντρο ανάπτυξης του ReadMe δεν επηρεάζεται.

2. 8 Σεπτεμβρίου 2026 στις 4:15 μ.μ. UTCinvestigating

   Καταφέραμε να επιλύσουμε την κατάσταση. Μπορεί να υπάρξει κάποια διαλείπουσα νωθρότητα για τα επόμενα λεπτά.

3. 8 Σεπτεμβρίου 2026 στις 4:16 μ.μ. UTCresolved

   Το περιστατικό λύθηκε.

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 21 Αυγούστου 2026 στις 4:36 μ.μ. UTCidentified

   Αυτή τη στιγμή βιώνουμε αργά αποτελέσματα αναζήτησης στους κόμβους πελατών

2. 21 Αυγούστου 2026 στις 6:21 μ.μ. UTCresolved

   Έχουμε επανα-indexed την αναζήτηση και την απόδοση έχει βελτιωθεί. Παρακαλώ e-mail υποστήριξη@readme.com αν εξακολουθείτε να βλέπετε θέματα με την αναζήτηση

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 24 Ιουλίου 2026 στις 12:22 μ.μ. UTCmonitoring

   Βιώνει υποβαθμισμένες επιδόσεις λόγω θεμάτων υποδομής τρίτων. Παρακολουθούμε αυτήν την κατάσταση και εργαζόμαστε για να διατηρήσουμε τη σταθερότητα στο τέλος μας.

2. 24 Ιουλίου 2026 στις 1:37 μ.μ. UTCresolved

   Το περιστατικό λύθηκε.

Αυτόματη μετάφραση από την επίσημη ενημέρωση του συμβάντος.

1. 17 Ιουνίου 2026 στις 3:28 μ.μ. UTCinvestigating

   We are currently investigating an incident related to API Reference pages.

2. 17 Ιουνίου 2026 στις 6:10 μ.μ. UTCresolved

   This incident was resolved and normal site function has been resolved

1. 28 Μαΐου 2026 στις 1:40 μ.μ. UTCinvestigating

   We're actively investigating this issue.

2. 28 Μαΐου 2026 στις 1:43 μ.μ. UTCidentified

   The issue has been identified and a fix is being implemented.

3. 28 Μαΐου 2026 στις 2:35 μ.μ. UTCidentified

   Systems are getting back up. We're continuing to work on a permanent fix for this issue.

4. 28 Μαΐου 2026 στις 3:27 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 28 Μαΐου 2026 στις 3:33 μ.μ. UTCmonitoring

   We are continuing to monitor for any further issues.

6. 28 Μαΐου 2026 στις 5:53 μ.μ. UTCmonitoring

   We are receiving reports of degraded performance and are actively investigating. We will provide updates as more information becomes available.

7. 28 Μαΐου 2026 στις 8:04 μ.μ. UTCmonitoring

   Systems appear stable and we are actively rolling out a series of fixes. We will continue to monitor and provide updates

8. 29 Μαΐου 2026 στις 1:49 π.μ. UTCmonitoring

   Systems remain stable. Improvements and fixes have been rolled out and we are continuing to monitor.

9. 29 Μαΐου 2026 στις 5:03 μ.μ. UTCmonitoring

   Systems remain stable, and we are continuing to monitor the situation. Bi-directional sync was on a maintenance job from 9:50 - 11:59 AM (ET) and is now operational.

10. 29 Μαΐου 2026 στις 6:36 μ.μ. UTCmonitoring

    Systems remain stable and our team continues to deploy targeted fixes. Work is ongoing to address degraded read performance across the system, including serving all 404s from cache. We’ll be actively monitoring over the weekend, and we will provide a full RCA next week.

11. 1 Ιουνίου 2026 στις 6:16 μ.μ. UTCresolved

    Our systems have been stable since Friday, May 29th. We're monitoring closely and improving spike detection to prevent recurrence and adding proactive capacity monitoring to detect admin dashboard degradation before it impacts customers. Full root cause analysis coming soon. Thanks for your patience and understanding.

1. 27 Μαΐου 2026 στις 1:51 μ.μ. UTCinvestigating

   We are currently investigating this issue.

2. 27 Μαΐου 2026 στις 2:52 μ.μ. UTCidentified

   The issue has been identified and a fix is being implemented.

3. 27 Μαΐου 2026 στις 3:57 μ.μ. UTCmonitoring

   We're slowly recovering and monitoring the situation.

4. 27 Μαΐου 2026 στις 5:08 μ.μ. UTCmonitoring

   We are monitoring the issue.

5. 27 Μαΐου 2026 στις 5:17 μ.μ. UTCmonitoring

   Updated 6/3: A routine configuration update coincided with the downtime window, which led us to initially identify it as the cause. Further investigation confirmed the two were unrelated. See the postmortem for full details.

6. 27 Μαΐου 2026 στις 5:43 μ.μ. UTCinvestigating

   We are seeing some slow performance, possibly 500 errors. investigating

7. 27 Μαΐου 2026 στις 5:47 μ.μ. UTCinvestigating

   We are continuing to investigate this issue.

8. 27 Μαΐου 2026 στις 6:02 μ.μ. UTCmonitoring

   Performance has improved, but we're still investigating the issue.

9. 27 Μαΐου 2026 στις 8:54 μ.μ. UTCmonitoring

   Performance and loading is still being affected, and we're in the process of rolling out fixes

10. 27 Μαΐου 2026 στις 10:37 μ.μ. UTCresolved

    This incident has been resolved.

11. 3 Ιουνίου 2026 στις 3:28 μ.μ. UTCpostmortem

    ### What Happened Beginning Tuesday, May 26, 2026, customers were experiencing slow loading and 503 errors across ReadMe-hosted docs and the admin dashboard. The outage was intermittent but recurring, with the worst periods hitting during business hours when traffic spiked. ### Root Cause An internal data backup process was generating excessive I/O on our storage layer. Under normal traffic conditions, this additional load was manageable. But when it coincided with peak customer traffic and elevated bot activity, total I/O demand exceeded system capacity, causing cascading request timeouts. The maintenance process ran on a recurring schedule, which is why the degradation followed a predictable pattern of spikes throughout each day. Separately, a surge in bot traffic to non-existent pages \(404s\) amplified the problem because those requests were not being served from cache. ### Resolution **Immediate fix:** We identified and disabled the maintenance process causing the excess I/O load. Within three hours, storage utilization returned to normal levels and remained stable. **Additional improvements shipped during the incident:** * Expanded caching across multiple layers, significantly reducing load on backend storage * Hardened 404 handling to serve error pages from cache instead of hitting the backend * Implemented rate limiting and IP-based protections against abusive bot traffic * Optimized several high-traffic API endpoints to reduce redundant backend calls * Added new monitoring and alerting for storage I/O thresholds ### Timeline May 26 - June 1, 2026 | Time | Status | Details | | --- | --- | --- | | Mon 5/26, 6:39 AM PDT | Investigating | Issue reported | | Mon 5/26, 7:26 AM PDT | Monitoring | Fix implemented, monitoring results | | Mon 5/26, 8:37 AM PDT | Resolved | Admin hub incident resolved | | Mon 5/26, 10:41 AM PDT | Investigating | Slow performance across customer hubs | | Mon 5/26, 10:49 AM PDT | Monitoring | Quick fix applied, investigating thorough fix | | Mon 5/26, 8:54 PM PDT | Resolved | Customer hub incident resolved | | Tue 5/27, 6:51 AM PDT | Investigating | Issue reported | | Tue 5/27, 7:52 AM PDT | Identified | Fix in progress | | Tue 5/27, 8:57 AM PDT | Monitoring | Slowly recovering | | Tue 5/27, 10:17 AM PDT | Update | Updated 6/3: A routine configuration update coincided with the downtime window, which led us to initially identify it as the cause. Further investigation confirmed the two were unrelated. See root cause and resolution above. | | Tue 5/27, 1:54 PM PDT | Update | Performance and loading still affected, rolling out fixes | | Tue 5/27, 3:37 PM PDT | Resolved | Incident resolved | | Wed 5/28, 6:40 AM PDT | Investigating | Issue reported | | Wed 5/28, 6:43 AM PDT | Identified | Fix being implemented | | Wed 5/28, 7:35 AM PDT | Update | Systems coming back up, working on permanent fix | | Wed 5/28, 8:27 AM PDT | Monitoring | Fix implemented, monitoring results | | Wed 5/28, 10:53 AM PDT | Update | Reports of degraded performance, actively investigating | | Wed 5/28, 1:04 PM PDT | Update | Systems appear stable, rolling out fixes | | Wed 5/28, 6:49 PM PDT | Monitoring | Improvements and fixes deployed, continuing to monitor | | Thu 5/29, 10:03 AM PDT | Monitoring | Systems stable. Bi-directional sync maintenance 9:50–11:59 AM ET. | | Thu 5/29, 11:36 AM PDT | Monitoring | Deploying targeted fixes. Serving all 404s from cache. Degraded read performance. | | Fri 5/30 | Monitoring | Monitoring continues | | Sat 5/31 | Monitoring | Weekend monitoring | | Mon 6/1, 11:16 AM PDT | Resolved | Root cause identified and resolved. Systems stable since Thursday, May 29. | ### Path Forward We are using this incident to make lasting improvements to reliability and incident response: * **Storage capacity and isolation:** Restructuring how background processes interact with production storage to eliminate contention under load. * **Caching and performance:** The caching improvements shipped during the incident are permanent. We are continuing to expand cache coverage across additional endpoints and page types. * **Bot and traffic protection:** Strengthening rate limiting and abuse detection to prevent bot traffic from contributing to backend load. * **Monitoring and alerting:** Adding proactive capacity monitoring with earlier thresholds so the team can intervene before customers are affected. * **Incident response:** Improving our internal processes for faster escalation and more frequent status page updates during multi-day incidents. ### Final Note During the incident, we posted an update referencing a platform update. That was our initial hypothesis based on timing. Further investigation confirmed it was unrelated. The change in question was a routine, isolated configuration update and had no impact on the outage or any other customers. We should have waited for confirmation before publishing it, and we're tightening our internal process for status page updates as a result. We know how critical your documentation is to your customers, and this level of disruption is not acceptable. We have already shipped meaningful improvements to prevent recurrence, and the work outlined above will continue through the coming weeks. If you have questions, reach out to your account team or contact [[email protected]](mailto:[email protected]).

1. 26 Μαΐου 2026 στις 5:41 μ.μ. UTCinvestigating

   We are experiencing slow performance across customer hubs

2. 26 Μαΐου 2026 στις 5:49 μ.μ. UTCmonitoring

   We have identified and quickly fixed the issue and are currently investigating a more thorough fix

3. 27 Μαΐου 2026 στις 3:54 π.μ. UTCresolved

   This incident has been resolved.

1. 26 Μαΐου 2026 στις 1:39 μ.μ. UTCinvestigating

   We are currently investigating this issue.

2. 26 Μαΐου 2026 στις 2:26 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 26 Μαΐου 2026 στις 3:37 μ.μ. UTCresolved

   This incident has been resolved.

1. 12 Μαΐου 2026 στις 2:15 μ.μ. UTCidentified

   We are investigating slowness across hubs.

2. 12 Μαΐου 2026 στις 7:38 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 12 Μαΐου 2026 στις 9:10 μ.μ. UTCresolved

   This incident has been resolved.

1. 11 Μαΐου 2026 στις 3:43 μ.μ. UTCinvestigating

   We are currently investigating this issue.

2. 11 Μαΐου 2026 στις 4:03 μ.μ. UTCidentified

   The issue has been identified and a fix is being implemented.

3. 11 Μαΐου 2026 στις 5:08 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 11 Μαΐου 2026 στις 6:34 μ.μ. UTCresolved

   This incident has been resolved.

1. 7 Μαΐου 2026 στις 11:43 μ.μ. UTCinvestigating

   We are currently investigating an issue creating changelogs

2. 8 Μαΐου 2026 στις 12:40 π.μ. UTCidentified

   We have identified the issue preventing the changelog creation page from rendering correctly, and we are working on a fix

3. 8 Μαΐου 2026 στις 3:02 π.μ. UTCmonitoring

   We have deployed the fix and are monitoring the results

4. 8 Μαΐου 2026 στις 3:18 π.μ. UTCresolved

   This incident has been resolved.

1. 28 Απριλίου 2026 στις 6:38 μ.μ. UTCinvestigating

   We are currently investigating an issue where customers are unable to create branches

2. 28 Απριλίου 2026 στις 7:02 μ.μ. UTCidentified

   We have identified the issue and are currently looking into a fix

3. 28 Απριλίου 2026 στις 7:31 μ.μ. UTCresolved

   Branches and versions can now be created successfully

1. 24 Απριλίου 2026 στις 12:17 μ.μ. UTCinvestigating

   We are currently investigating this issue.

2. 24 Απριλίου 2026 στις 12:29 μ.μ. UTCinvestigating

   We are continuing to investigate this issue.

3. 24 Απριλίου 2026 στις 1:42 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 24 Απριλίου 2026 στις 3:11 μ.μ. UTCresolved

   This incident has been resolved.

1. 22 Απριλίου 2026 στις 2:35 μ.μ. UTCinvestigating

   We are currently investigating downtime impacting admin users.

2. 22 Απριλίου 2026 στις 2:40 μ.μ. UTCidentified

   An issue has been identified with a third-party provider. A fix is being implemented.

3. 22 Απριλίου 2026 στις 2:53 μ.μ. UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 22 Απριλίου 2026 στις 2:56 μ.μ. UTCmonitoring

   Admin dashboard is recovering and we are continuing to monitor for further issues.

5. 22 Απριλίου 2026 στις 2:59 μ.μ. UTCmonitoring

   Fix has been applied and admin requests have recovered. We are continuing to monitor for any further issues.

6. 22 Απριλίου 2026 στις 4:36 μ.μ. UTCresolved

   Issues with admin requests have been resolved.

1. 22 Απριλίου 2026 στις 2:59 π.μ. UTCinvestigating

   We are currently investigating performance issues across the platform.

2. 22 Απριλίου 2026 στις 3:08 π.μ. UTCidentified

   We've discovered the issue and have implemented a quick fix

3. 22 Απριλίου 2026 στις 3:43 π.μ. UTCresolved

   Fix has been implemented and performance has stabilized.

1. 20 Απριλίου 2026 στις 8:05 μ.μ. UTCidentified

   The admin interface is experiencing slower than expected response times.

2. 20 Απριλίου 2026 στις 9:16 μ.μ. UTCmonitoring

   Performance has returned to normal, and we are continuing to monitor.

3. 20 Απριλίου 2026 στις 9:20 μ.μ. UTCresolved

   This incident has been resolved.

1. 16 Απριλίου 2026 στις 4:07 μ.μ. UTCinvestigating

   We are getting reports of slow performance and 500 errors when loading pages

2. 16 Απριλίου 2026 στις 4:57 μ.μ. UTCmonitoring

   We've stabilized our platform and our response times have improved. We are currently monitoring the situation.

3. 16 Απριλίου 2026 στις 7:25 μ.μ. UTCresolved

   Performance has stabilized and we are no longer returning errors upon loading pages.