https://status.lyrenth.comIncidents and maintenance for the Lyrenth API and website.Fri, 11 Sep 2026 04:57:05 +0000Resolved. The provider restored their Vienna network and all services recovered: the API is fully serving, reads are answering from the index, and the crawler resumed. No data was lost or affected at any point. Total API impact was several hours of unavailability; during the later part of the outage the API answered with clear errors stating that requests were not processed and not billed, and that remains true for the whole incident: no request during the outage was billed.2026-08-21 18:41 CEST2026-08-212026-08-21 18:41 CESThttps://status.lyrenth.comPartial connectivity is returning: some of our infrastructure is reachable again, but the API is still unavailable while the provider's recovery continues. The website stays up and no data is affected. Next update when the API is back or the situation changes.2026-08-21 19:50 CEST2026-08-212026-08-21 19:50 CESThttps://status.lyrenth.comThe provider's recovery attempts have not held: connectivity returned briefly for parts of the infrastructure and dropped again. All API services remain unavailable while their network engineers keep working. The website stays up and no data is affected.2026-08-21 19:05 CEST2026-08-212026-08-21 19:05 CESThttps://status.lyrenth.comOur hosting provider has confirmed a network outage at their Vienna location. All API endpoints (api.lyrenth.com) are unreachable. The website stays up. No data is affected: our database archives are stored with a separate provider and are intact.2026-08-21 15:20 CEST2026-08-212026-08-21 15:20 CESThttps://status.lyrenth.comWe are investigating connectivity problems affecting the API.2026-08-21 14:55 CEST2026-08-212026-08-21 14:55 CESThttps://status.lyrenth.comAdded to this history after the fact. This status page was published on 21 August, so this incident happened before the page existed; we are recording it here rather than letting the history begin on the day we started publishing. The times come from our own request records and are accurate to a few minutes. Because we were not yet measuring uptime independently on that day, this day is shown in the history but is not counted in the uptime percentage above.2026-08-222026-08-052026-08-22https://status.lyrenth.comResolved. A second, related fault appeared about two hours after the first fix and made the API unavailable again for about 6 minutes. Both are now corrected and we have added an automatic check that warns us long before this condition can return. Total time unavailable on this day was about 19 minutes across the two interruptions. No data was lost or affected, and no request during either interruption was billed.2026-08-05 17:54 CEST2026-08-052026-08-05 17:54 CESThttps://status.lyrenth.comThe API stopped answering for about 13 minutes during routine maintenance. Reads and the MCP endpoint were unavailable for the same period. The website stayed up, although signed-in pages could not load live data while the API was down. The cause was an internal limit that had been reached as our systems grew, and it has been raised.2026-08-05 15:42 CEST2026-08-052026-08-05 15:42 CESThttps://status.lyrenth.com