RelayPath
INCIDENT #RP-2025-048 Filed 14 min ago

Application Portal — Status Update

System Anomaly Detected in the RelayPath Application Portal

By Grace Okafor Site Reliability Engineer Updated 14:32 GMT

We've encountered an unexpected disruption. The RelayPath Application Portal is temporarily unable to process your request. Our engineers have been notified and are actively investigating the root cause. This page will be updated as new information becomes available.

01 / Possible Causes

Based on preliminary telemetry
C1

Intermittent network instability on your end may prevent the portal from responding as expected.

C2

An expired or invalid session token, or a link that has since been rotated for security.

C3

The requested resource or identifier is not currently recognized by our system registry.

C4

A transient server issue within our edge infrastructure. This is being monitored closely.

99.98% uptime YTD
12,400 teams on RelayPath
148 avg. response (ms)
3.2 yr Avg. incident count

03 / Our Incident Process

How we resolve anomalies
A

Detection & Triage

Automated health checks and user reports funnel into a central queue. We triage within 5 minutes, 24/7, and assign a dedicated incident lead.

B

Isolation & Diagnosis

We isolate the blast radius, replay traffic, and inspect edge logs. For this incident, we've narrowed the fault to a config propagation issue (ID: CFG-419).

C

Remediation & Review

Once patched, we run a full regression suite and publish a post-mortem. Open communication is non-negotiable — no silent fixes.

"RelayPath's status pages are refreshingly direct. During our last incident, I knew exactly what was happening and when to expect a fix. No corporate fog."

Marcus Keller

CTO, Northwind Logistics

Frequently Asked Questions

We know anomalies cause friction. Here are the answers to the questions our support team hears most during an incident.

Yes. Any request that reached our API gateway before the anomaly was placed into a durable queue. Once the config propagation is fixed, queued requests will be processed automatically. No manual resubmission required.

Not at all. The expiry is a security feature. Tokens rotate every 15 minutes. If your token lapsed, simply refresh the page and you'll be issued a new one. Your data remains encrypted and intact.

The top of this page will show a green "Operational" badge the moment we consider the incident resolved. We'll also send an email to all affected workspace owners. If you'd like a head start, refresh the page in a minute or two.

Still experiencing issues?

Our support team is available around the clock. Reach out with your incident ID and we'll prioritise your ticket immediately.

Incident reference

RP-2025-048

Diagnosis in progress — 40% complete