Flexpa - Notice history

All systems operational

api.flexpa.com - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

link.flexpa.com - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

my.flexpa.com - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

flexpa.com/docs - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

portal.flexpa.com - Operational

100.0% uptime
Feb 2025 · 100.0%Mar · 100.0%Apr · 100.0%

Previous page

Next page

Feb 2025
Mar 2025
Apr 2025

Notice history

View current status

Apr 2025

Intermittent API errors
ResolvedDegraded performance41 minutes
  • Resolved
    UTC
    Resolved

    This incident has been resolved. During the incident period 2.9% of requests to Flexpa API failed. The degraded state made the issue difficult to diagnose at first. We're reviewing observability improvements to reduce this in the future.

  • Monitoring
    UTC
    Monitoring

    Fix has been deployed and we are currently monitoring

  • Identified
    UTC
    Identified

    Issue identified and a fix is being deployed

  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.

Mar 2025

No notices reported this month

Feb 2025

Pagination Resolution
Resolved3 hours
  • Resolved
    UTC
    Resolved

    We have completed our monitoring and can validate resolution of this issue.

  • Monitoring
    UTC
    Monitoring

    A fix has been deployed and we are monitoring.

  • Identified
    UTC
    Identified

    `Bundle.link[0].next` values are returning incorrect base URL / hostname values.

    Requests made to these values as documented in our pagination led to timeouts in the period of Jan 20 to Feb 5.

    We are currently deploying a fix.

Previous

Feb 2025 to Apr 2025

Next