EasyRedir Outage History

EasyRedir is up right now

Pingoru has recorded 13 incidents for EasyRedir: 1 in the last 12 months and 0 in the last 90 days.

Source: status.easyredir.com

13incidents recorded
1last 12 months
0last 90 days
18 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking EasyRedir in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 568 (0%)

Incidents, newest first

Minor December 18, 2025 Delayed analytics in management dashboard 18h 23m Dashboard, Analytics

Started Dec 18, 2025, 01:48 AM UTC· resolved Dec 18, 2025, 08:11 PM UTC

  1. investigating Dec 18, 2025, 01:48 AM UTC

    There is currently a delay in displaying daily analytics within the dashboard. We are investigating the issue and will provide an update within 24 hours. We note that analytics continue to be ingested and all missing historical analytics will be available once the issue is resolved.

  2. monitoring Dec 18, 2025, 05:40 PM UTC

    We are currently processing yesterday's analytics data. It should be visible in the urllo dashboard within the next few hours. Daily email updates will be sent when the data is available. We will continue to monitor and provide further updates as appropriate.

  3. resolved Dec 18, 2025, 08:11 PM UTC

    All prior analytics data is now available in the urllo dashboard. This issue is now resolved.

Read the full incident report →

Minor August 28, 2025 Investigating increased latency on redirects. 22h 5m Global Edge (HTTP traffic), Global Edge (HTTPS traffic), US West Edge (HTTP traffic), US West Edge (HTTPS traffic)

Started Aug 28, 2025, 06:04 PM UTC· resolved Aug 29, 2025, 04:10 PM UTC

  1. investigating Aug 28, 2025, 06:04 PM UTC

    Our Incident Response Team (IRT) is investigating brief increases in latency that may be affecting some redirects. Next update within 24 hours.

  2. identified Aug 28, 2025, 06:21 PM UTC

    We’ve identified the source of the elevated tail latencies and are working to resolve the issue. Next update within 24 hours.

  3. resolved Aug 29, 2025, 04:10 PM UTC

    Increased latency on redirects has been resolved.

Read the full incident report →

Minor August 25, 2025 Investigating increased latency on redirects 1d 18h Global Edge (HTTP traffic), Global Edge (HTTPS traffic), US West Edge (HTTP traffic), US West Edge (HTTPS traffic)

Started Aug 25, 2025, 10:24 PM UTC· resolved Aug 27, 2025, 05:05 PM UTC

  1. investigating Aug 25, 2025, 10:24 PM UTC

    Our Incident Response Team (IRT) is investigating a potential service disruption. Users may be experiencing increased latency on redirects. We will post additional updates as new information is available.

  2. monitoring Aug 26, 2025, 12:11 AM UTC

    Our Incident Response Team (IRT) has deployed a fix to resolve the increased latency on redirects. We’re monitoring to ensure normal performance continues. Next update within the next 24 hours.

  3. monitoring Aug 26, 2025, 06:24 PM UTC

    We are continuing to monitor for any further issues. Next update within the next 24 hours.

  4. resolved Aug 27, 2025, 05:05 PM UTC

    Tail latencies on redirects have returned to normal levels.

Read the full incident report →

Minor August 11, 2025 Investigating redirector latency 3d 21h Global Edge (HTTP traffic), Global Edge (HTTPS traffic), US West Edge (HTTP traffic), US West Edge (HTTPS traffic)

Started Aug 11, 2025, 06:48 PM UTC· resolved Aug 15, 2025, 04:06 PM UTC

  1. investigating Aug 11, 2025, 06:48 PM UTC

    We are investigating brief increases in latency that may be affecting some redirects.

  2. investigating Aug 11, 2025, 10:19 PM UTC

    Our Incident Response Team (IRT) is continuing to investigate this issue. You can expect to receive an update within the next 24 hours.

  3. investigating Aug 12, 2025, 05:03 PM UTC

    Our Incident Response Team (IRT) has deployed a fix that has resolved the degraded performance. We are continuing to investigate the root cause. Next update will be provided within 24 hours.

  4. investigating Aug 13, 2025, 03:57 AM UTC

    Users may be experiencing brief increases in latency on some redirects. Our IRT continues to investigate the issue. Next update will be provided within 24 hours.

  5. identified Aug 13, 2025, 10:02 PM UTC

    We are deploying changes to improve brief periods of intermittent latency. Next update within 24 hours.

  6. monitoring Aug 14, 2025, 03:24 PM UTC

    Our Incident Response Team (IRT) has deployed a fix for the brief increases in latency. We’re monitoring to ensure normal performance continues. Next update within 24 hours.

  7. resolved Aug 15, 2025, 04:06 PM UTC

    The brief increases in latency affecting some redirects have been resolved.

Read the full incident report →

Notice August 10, 2025 Increased latency –

Started Aug 10, 2025, 08:00 PM UTC· resolved Aug 10, 2025, 08:00 PM UTC

  1. resolved Aug 11, 2025, 01:56 AM UTC

    A network-related issue with urllo’s redirector may have caused some customers to experience increased latency for a short period of time. Services are back to normal and the issue is resolved.

Read the full incident report →

Minor October 25, 2024 Request analytics data is delayed 5h 30m Dashboard

Started Oct 25, 2024, 04:43 PM UTC· resolved Oct 25, 2024, 10:13 PM UTC

  1. investigating Oct 25, 2024, 04:43 PM UTC

    We are currently investigating an issue that is delaying the availability of some types of request analytics in our dashboard, and also preventing the delivery of recurring analytics emails.

  2. identified Oct 25, 2024, 07:44 PM UTC

    We have identified the root cause of the issue and are working on implementing a fix. This should be completed within the next few hours. We will post an update when the issue has been solved.

  3. monitoring Oct 25, 2024, 09:04 PM UTC

    A fix has been implemented and we continue to monitor the results.

  4. monitoring Oct 25, 2024, 10:12 PM UTC

    The issue has been resolved.

  5. resolved Oct 25, 2024, 10:13 PM UTC

    This incident has been resolved.

Read the full incident report →