Is Latitude.sh down?

Last checked 10m ago
Current status
Latitude.sh is up

No incidents right now.

Official status page: https://status.latitude.sh · Polled every 5 minutes · 36 components tracked

Latitude.sh is operational right now. Last checked 10m ago; the most recent incident resolved 3d ago.

Real-time Latitude.sh status, recent outages, and incident history — pulled directly from Latitude.sh's official status page at https://status.latitude.sh every 5 minutes. Pingoru tracks 36 Latitude.sh services and has captured 17 incidents in the last 90 days (99.66% uptime). Get email, Slack, Discord, or webhook alerts the moment Latitude.sh reports a new incident — free for 5 monitors, no credit card.

Users who monitor Latitude.sh also follow these Hosting services: Pantheon CodeTwo DNSimple Wix I Want My Name Hostinger Kinsta Liquid Web Flywheel GearHost View all 6,000+ providers
Latitude.sh uptime 99.66% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h
    Started Sep 10, 2026, 10:03 PM UTC · Resolved Sep 11, 2026, 12:03 AM UTC
    SAO
    Timeline · 4 updates
    • investigating · Sep 10, 2026, 10:03 PM UTC

      Network issue affecting services in our Sao Paulo location, identified today at approximately 21:00 UTC. Our Network Operations team is actively investigating the issue and working to fully restore normal conditions.

    • investigating · Sep 10, 2026, 10:13 PM UTC

      We are continuing to investigate this issue.

    • monitoring · Sep 10, 2026, 11:37 PM UTC

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

    • resolved · Sep 11, 2026, 12:03 AM UTC

      A link degradation was identified with one of our providers. As a mitigation measure, traffic from the data center was rerouted through alternative links. Following continuous monitoring, the link has stabilized and performance has returned to normal.

    Latest: A link degradation was identified with one of our providers. As a mitigation measure, traffic from the data center was rerouted through alternative links. Following continuous moni…

  2. Resolved 23h 37m
    Started Aug 08, 2026, 12:17 AM UTC · Resolved Aug 08, 2026, 11:54 PM UTC
    LONLON2
    Timeline · 5 updates
    • investigating · Aug 08, 2026, 12:17 AM UTC

      We are currently investigating this issue.

    • investigating · Aug 08, 2026, 12:29 AM UTC

      We are continuing to investigate this issue.

    • identified · Aug 08, 2026, 03:05 AM UTC

      Some devices are being recovered. Our team are still working with the DCO to fully recover the site.

    • identified · Aug 08, 2026, 11:06 AM UTC

      Several servers have been recovered but the full extension of the site is still being worked on at the moment. Our team is still working with the DCO for the full resolution.

    • resolved · Aug 08, 2026, 11:54 PM UTC

      This incident has been resolved. Our team will keep the communication for the affected customers via ongoing tickets.

    Latest: This incident has been resolved. Our team will keep the communication for the affected customers via ongoing tickets.

  3. Resolved 1h 16m
    Started Jun 26, 2026, 10:09 PM UTC · Resolved Jun 26, 2026, 11:26 PM UTC
    NYC
    Timeline · 3 updates
    • investigating · Jun 26, 2026, 10:09 PM UTC

      We are currently investigating this issue.

    • monitoring · Jun 26, 2026, 11:09 PM UTC

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

    • resolved · Jun 26, 2026, 11:26 PM UTC

      We experienced an issue on one of our border routers in New York. The router did not fail completely, however some services were impacted, which required a reboot to fully restore normal operation. During this time, our redundant infrastructure ensured that only part of the traffic was affected. Traffic is now fully stable, we are monitoring the health status closely and will share a full update once our investigation is complete.

    Latest: We experienced an issue on one of our border routers in New York. The router did not fail completely, however some services were impacted, which required a reboot to fully restore …

  4. Resolved 12h 8m
    Started Jun 25, 2026, 09:16 AM UTC · Resolved Jun 25, 2026, 09:25 PM UTC
    Automation Tool
    Timeline · 3 updates
    • investigating · Jun 25, 2026, 09:16 AM UTC

      We are currently investigating this issue and will provide more details as soon as they are available.

    • monitoring · Jun 25, 2026, 11:40 AM UTC

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

    • resolved · Jun 25, 2026, 09:25 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 11h 5m
    Started Jun 23, 2026, 10:23 PM UTC · Resolved Jun 24, 2026, 09:29 AM UTC
    SAOSP1APIMIA2CHILAXNYCSYDDALRemote access
    Timeline · 4 updates
    • investigating · Jun 23, 2026, 10:23 PM UTC

      We are currently investigating this issue.

    • investigating · Jun 23, 2026, 10:41 PM UTC

      We have a preliminary diagnosis that the incident was caused by a power outage affecting all the customers on the same floor. We are pushing the DC operator for an update. Is it impacting all of our services, Dashboard and API.

    • monitoring · Jun 24, 2026, 12:35 AM UTC

      Services have been restored following a power outage. We are currently monitoring the environment closely and awaiting final confirmation from the data center team. Further updates to follow.

    • resolved · Jun 24, 2026, 09:29 AM UTC

      This incident has been resolved. We will follow up with a post-mortem as soon as a complete RCA is finished between Latitude.sh and our DCO.

    Latest: This incident has been resolved. We will follow up with a post-mortem as soon as a complete RCA is finished between Latitude.sh and our DCO.

See the full Latitude.sh outage history

2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Latitude.sh outage history →

Or sign up free to get alerts when Latitude.sh breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 7 incidents View full outage history →