Incidents reported on status page for Ligate Labs https://status.ligate.io/ https://d1lppblt9t2x15.cloudfront.net/logos/808fe57c51080520d0a70d47e361c35f.png https://status.ligate.io/ en https://status.ligate.io/ Mon, 08 Jun 2026 22:01:20 +0000 https://status.ligate.io/#973e640f6f8d4b310245d1ae80de2947c9595cab81ae458dedbd07f8a22c9595 Ligate HTTP API recovered https://status.ligate.io/ Mon, 08 Jun 2026 21:59:05 +0000 https://status.ligate.io/#973e640f6f8d4b310245d1ae80de2947c9595cab81ae458dedbd07f8a22c9595 Ligate HTTP API went down https://status.ligate.io/incident/900118 Sun, 24 May 2026 21:06:25 -0000 https://status.ligate.io/incident/900118#ebbe06a95667b45cfa416d560f349192c1525a1c00509f9127b566e51b01b7f6 Explorer indexer is fully caught up. `indexer_height` and `head_height` are both at 134000, lag is 0. The explorer is now reflecting current chain state. Marking resolved. This closes out the Railway outage incident opened 2026-05-19 22:41 UTC. https://status.ligate.io/incident/900118 Wed, 20 May 2026 10:15:46 -0000 https://status.ligate.io/incident/900118#f01173e5b44f82d3f4bf35d371335d3a8b8ec2df65e6a3e67512a31c83fdf980 Explorer indexer is fully caught up. `indexer_height` is 69936 against `head_height` 69937 (1-slot real-time lag). Block, transaction, and attestation data on explorer.ligate.io are current. Closing the explorer card out. Incident resolved end to end. https://status.ligate.io/incident/900118 Wed, 20 May 2026 01:39:10 -0000 https://status.ligate.io/incident/900118#13c1b89905215cfc64a1f7c3961663cd7602e2af9f25d7f6364021a0a85cf367 api.ligate.io is reachable again. The outage lasted 2 hours 57 minutes (original incident opened 2026-05-19 22:41 UTC). Railway restored access to their edge network and our API service is responding. The indexer task inside the API service has not yet caught up after the restart. `indexer_height` is currently null while `head_height` is at 64777. The explorer page itself is reachable, but recent block and transaction data will be empty or stale until the indexer reconnects to Postgres and works through the backlog. Marking the explorer as degraded. A follow-up update will confirm when the indexer is back at zero lag. https://status.ligate.io/ Wed, 20 May 2026 01:38:20 +0000 https://status.ligate.io/#3d2e3604b28ed567af60b59c2c9533110822460ecde36e2027f3ee815afe623b Ligate HTTP API recovered https://status.ligate.io/incident/900118 Wed, 20 May 2026 01:18:38 -0000 https://status.ligate.io/incident/900118#43b4025f41251d301fa34e3aaa7a3450424a682f4f35dfc341d430f6ad67cc5d api.ligate.io is still unreachable, roughly 2 hours 37 minutes into the outage. No change on our end. Latest from Railway, dated 2026-05-20 00:37 UTC: their incident remains at "identified" status. Per their status page, partial Google Cloud access has been restored and they are working directly with Google support to bring back the dashboard, API, and control plane. No ETA was provided by Railway. Next update from us within 60 minutes, or sooner if api.ligate.io recovers. https://status.ligate.io/incident/900118 Wed, 20 May 2026 00:13:38 -0000 https://status.ligate.io/incident/900118#c6dc14277a228e6bd821b55f9da1b54bc933bedf113528e4bba25cbb3ae66c82 api.ligate.io is still unreachable, roughly 65 minutes into the outage. No change on our end. Upstream update from Railway: their incident has moved from "investigating" to "identified." Per their status page, the root cause is that Google Cloud blocked Railway's account, taking down portions of Railway's edge network. Railway has escalated with Google and reports partial access restoration is underway. Our API service depends on Railway's edge, so it will return when Railway's GCP access is fully restored. Next update from us within 60 minutes, or sooner if api.ligate.io recovers. https://status.ligate.io/incident/900118 Tue, 19 May 2026 22:47:52 -0000 https://status.ligate.io/incident/900118#a11cc5ffb25161e6ed9c7ce755b9f92b48cb785c4ed535e86a736b1e00c89a69 Flipping the explorer to degraded. explorer.ligate.io itself is reachable (the Next.js page renders on Vercel), but it sources block, transaction, and account data from api.ligate.io, which is down with the Railway outage. The page loads, but data panels will be empty or stale until Railway recovers. API remains down. Same incident, no new upstream signal from Railway yet. https://status.ligate.io/incident/900118 Tue, 19 May 2026 22:41:12 -0000 https://status.ligate.io/incident/900118#a442aba737c0d0e434c4de44e0c07766d78c79806791a7f5c031d180bdc3c2ab api.ligate.io is currently unreachable. Requests time out before reaching our service. Upstream cause: Railway, which hosts the API service, is reporting a major edge network outage on its public status page (status.railway.com). Their incident is marked "investigating" and lists "no healthy upstream" and "unconditional drop overload" errors across affected projects. Railway's own dashboard and management API are also impaired, so we cannot redeploy or fail over while their edge is down. Unaffected: chain RPC (rpc.ligate.io), explorer (explorer.ligate.io), and the websites (ligate.io, themisra.xyz). The chain itself is producing blocks normally. Next update from us within 60 minutes, or sooner if Railway moves their incident to "identified" or "monitoring." https://status.ligate.io/ Tue, 19 May 2026 22:19:32 +0000 https://status.ligate.io/#3d2e3604b28ed567af60b59c2c9533110822460ecde36e2027f3ee815afe623b Ligate HTTP API went down https://status.ligate.io/ Mon, 18 May 2026 21:16:27 +0000 https://status.ligate.io/#63cae08e9414611bc98130dbe30a0cfbf1ea33789dd23ec6450fab7634fd431e themisra.xyz recovered https://status.ligate.io/ Mon, 18 May 2026 21:13:26 +0000 https://status.ligate.io/#63cae08e9414611bc98130dbe30a0cfbf1ea33789dd23ec6450fab7634fd431e themisra.xyz went down https://status.ligate.io/incident/898058 Sun, 17 May 2026 23:15:55 -0000 https://status.ligate.io/incident/898058#45660c416619739e4461692c081702bf60868ea6def83088190125013509f3e7 Indexer fully caught up. `indexer_height` and `head_height` are both at 34586, lag is 0. Explorer is now reflecting current chain state. Marking resolved. https://status.ligate.io/incident/898058 Sun, 17 May 2026 16:45:16 -0000 https://status.ligate.io/incident/898058#6e5d8bd3f08e2a869f218a2b87fbc6e92ef86c416928d10e5acd6c07aec65b23 The explorer indexer is roughly 27,000 slots behind the chain head following the v0.2.0 deploy. The page itself is reachable; recent activity will appear with a delay until the indexer is fully caught up. Current closure rate puts full sync at roughly 5 to 6 hours from now. A follow-up update will confirm when the indexer catches up. No action required. https://status.ligate.io/incident/898057 Sun, 17 May 2026 16:45:10 -0000 https://status.ligate.io/incident/898057#adc592b74c7a32a26c78e6056db3d0de5172062922ba24163ba84e0c88772f96 ligate-devnet-1 is now running chain v0.2.0. Breaking wire-format change. AttestationId collapses to a single `lat1...` bech32m hash (32 bytes), replacing the v0.1.x compound `lsc1...:lph1...` form. Any client built against v0.1.x will not interoperate; rebuild against the v0.2.0 crates. Endpoints unchanged. `chain_hash` unchanged from v0.1.3. Full notes are in the CHANGELOG. https://status.ligate.io/incident/897974 Sun, 17 May 2026 12:54:38 -0000 https://status.ligate.io/incident/897974#f49cb0aeb4036d6c1250a574c2dff4e22688973b39bf798fe255017dba1413bf The chain is live on Celestia Mocha-testnet. Public RPC, indexer API, and explorer are all reachable. This page tracks every public Ligate service from here. Incidents, scheduled maintenance, and updates will land here first. Chain RPC: https://rpc.ligate.io HTTP API: https://api.ligate.io Explorer: https://explorer.ligate.io Source: https://github.com/ligate-io