Actualmente estamos investigando por qué las páginas muestran 404
identified
Hemos identificado el problema y estamos trabajando en una solución
monitoring
La solución ha sido implementada y actualmente estamos implementando los servidores operativos. Puede haber unos 404s caché, así que por favor avísele si sigues corriendo en problemas
resolved
Los proyectos deben estar mostrando de nuevo. Póngase en contacto con [email protected] si todavía se encuentra en errores de 404.
Traducido automáticamente desde la actualización oficial del incidente.
Rendimiento degradado a través de los centros
Comenzó 22 de septiembre de 2026 a las 14:22 UTC · 2h 22m
IssuesIncidente menor
Componentes afectados
Admin DashboardReadMe Knowledge BaseReadMe Hubs
investigating
Actualmente estamos investigando la latencia elevada y los tiempos de respuesta lentos que afectan a los centros. Trabajando activamente para identificar la causa raíz y restaurar el servicio normal.
monitoring
Se ha implementado una solución y actualmente estamos monitoreando los resultados. El rendimiento debe volver a la normalidad.
monitoring
Hemos identificado factores adicionales y estamos trabajando activamente para solucionarlos.
monitoring
Continuamos monitoreando cualquier otro problema.
resolved
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
Interfaz de Admin
Comenzó 8 de septiembre de 2026 a las 16:04 UTC · 12m
OutageIncidente crítico
Componentes afectados
Admin Dashboard
investigating
Nuestra interfaz Admin está experimentando un outage. La capacidad de los usuarios finales para visitar su centro de desarrollo ReadMe no es afectada.
investigating
Pudimos resolver la situación. Puede haber alguna sluggishness intermitente durante los próximos minutos.
resolved
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
Búsqueda lenta dentro de los centros de clientes
Comenzó 21 de agosto de 2026 a las 16:36 UTC · 1h 45m
IssuesIncidente menor
Componentes afectados
ReadMe Hubs
identified
Actualmente estamos experimentando resultados de búsqueda lentas a través de centros de clientes
resolved
Hemos re-indexado la búsqueda y el rendimiento ha mejorado. Por favor, e-mail [email protected] si sigues viendo problemas con la búsqueda
Traducido automáticamente desde la actualización oficial del incidente.
Rendimiento degradado debido a cuestiones de infraestructura de terceros
Comenzó 24 de julio de 2026 a las 12:22 UTC · 1h 16m
IssuesIncidente menor
Componentes afectados
Admin DashboardReadMe Hubs
monitoring
Ampliar el rendimiento degradado debido a problemas de infraestructura de terceros. Estamos monitoreando esta situación y trabajando para mantener la estabilidad en nuestro fin.
resolved
Este incidente ha sido resuelto.
Traducido automáticamente desde la actualización oficial del incidente.
API Reference Degradation
Comenzó 17 de junio de 2026 a las 15:28 UTC · 2h 41m
Pending
investigating
We are currently investigating an incident related to API Reference pages.
resolved
This incident was resolved and normal site function has been resolved
Refactored Hubs Down
Comenzó 28 de mayo de 2026 a las 13:40 UTC · 4d 4h
OutageIncidente mayor
Componentes afectados
Admin DashboardReadMe Knowledge BaseReadMe Hubs
investigating
We're actively investigating this issue.
identified
The issue has been identified and a fix is being implemented.
identified
Systems are getting back up. We're continuing to work on a permanent fix for this issue.
monitoring
A fix has been implemented and we are monitoring the results.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are receiving reports of degraded performance and are actively investigating. We will provide updates as more information becomes available.
monitoring
Systems appear stable and we are actively rolling out a series of fixes. We will continue to monitor and provide updates
monitoring
Systems remain stable. Improvements and fixes have been rolled out and we are continuing to monitor.
monitoring
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.
monitoring
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.
resolved
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.
ReadMe Refactored Outage
Comenzó 27 de mayo de 2026 a las 13:51 UTC · 8h 47m
OutageIncidente crítico
Componentes afectados
Admin DashboardReadMe Knowledge BaseReadMe Hubs
investigating
We are currently investigating this issue.
identified
The issue has been identified and a fix is being implemented.
monitoring
We're slowly recovering and monitoring the situation.
monitoring
We are monitoring the issue.
monitoring
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.
investigating
We are seeing some slow performance, possibly 500 errors. investigating
investigating
We are continuing to investigate this issue.
monitoring
Performance has improved, but we're still investigating the issue.
monitoring
Performance and loading is still being affected, and we're in the process of rolling out fixes
resolved
This incident has been resolved.
postmortem
### 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]).
Slow performance across customer hubs
Comenzó 26 de mayo de 2026 a las 17:41 UTC · 10h 13m
OutageIncidente mayor
Componentes afectados
Admin DashboardReadMe Hubs
investigating
We are experiencing slow performance across customer hubs
monitoring
We have identified and quickly fixed the issue and are currently investigating a more thorough fix
resolved
This incident has been resolved.
Degraded performance across Admin Hubs
Comenzó 26 de mayo de 2026 a las 13:39 UTC · 1h 58m
OutageIncidente mayor
Componentes afectados
Admin DashboardReadMe Knowledge BaseReadMe Hubs
investigating
We are currently investigating this issue.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
Degraded performance across Admin Hubs
Comenzó 12 de mayo de 2026 a las 14:15 UTC · 6h 55m
IssuesIncidente menor
Componentes afectados
Admin DashboardReadMe Knowledge BaseReadMe Hubs
identified
We are investigating slowness across hubs.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
Degraded performance across Admin Hubs
Comenzó 11 de mayo de 2026 a las 15:43 UTC · 2h 51m
IssuesIncidente menor
Componentes afectados
Admin DashboardReadMe Knowledge BaseReadMe Hubs
investigating
We are currently investigating this issue.
identified
The issue has been identified and a fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
Issues Creating New Changelogs
Comenzó 7 de mayo de 2026 a las 23:43 UTC · 3h 35m
OutageIncidente crítico
Componentes afectados
Admin Dashboard
investigating
We are currently investigating an issue creating changelogs
identified
We have identified the issue preventing the changelog creation page from rendering correctly, and we are working on a fix
monitoring
We have deployed the fix and are monitoring the results
resolved
This incident has been resolved.
Creating branches is resulting in 500 errors
Comenzó 28 de abril de 2026 a las 18:38 UTC · 52m
IssuesIncidente menor
Componentes afectados
ReadMe Hubs
investigating
We are currently investigating an issue where customers are unable to create branches
identified
We have identified the issue and are currently looking into a fix
resolved
Branches and versions can now be created successfully
Service disruption
Comenzó 24 de abril de 2026 a las 12:17 UTC · 2h 54m
OutageIncidente crítico
Componentes afectados
ReadMe Knowledge BaseReadMe Hubs
investigating
We are currently investigating this issue.
investigating
We are continuing to investigate this issue.
monitoring
A fix has been implemented and we are monitoring the results.
resolved
This incident has been resolved.
Admin downtime
Comenzó 22 de abril de 2026 a las 14:35 UTC · 2h 1m
OutageIncidente mayor
Componentes afectados
Admin DashboardReadMe Hubs
investigating
We are currently investigating downtime impacting admin users.
identified
An issue has been identified with a third-party provider. A fix is being implemented.
monitoring
A fix has been implemented and we are monitoring the results.
monitoring
Admin dashboard is recovering and we are continuing to monitor for further issues.
monitoring
Fix has been applied and admin requests have recovered. We are continuing to monitor for any further issues.
resolved
Issues with admin requests have been resolved.
Slow performance, increased 500 errors upon page load
Comenzó 22 de abril de 2026 a las 2:59 UTC · 44m
IssuesIncidente menor
Componentes afectados
Admin DashboardReadMe Knowledge BaseReadMe Hubs
investigating
We are currently investigating performance issues across the platform.
identified
We've discovered the issue and have implemented a quick fix
resolved
Fix has been implemented and performance has stabilized.
Increased Admin Response Times
Comenzó 20 de abril de 2026 a las 20:05 UTC · 1h 16m
IssuesIncidente menor
Componentes afectados
Admin Dashboard
identified
The admin interface is experiencing slower than expected response times.
monitoring
Performance has returned to normal, and we are continuing to monitor.
resolved
This incident has been resolved.
Slow performance / 500 error pages
Comenzó 16 de abril de 2026 a las 16:07 UTC · 3h 18m
IssuesIncidente menor
Componentes afectados
ReadMe Hubs
investigating
We are getting reports of slow performance and 500 errors when loading pages
monitoring
We've stabilized our platform and our response times have improved. We are currently monitoring the situation.
resolved
Performance has stabilized and we are no longer returning errors upon loading pages.
