Wilmington Metro Real-Time Service Alerts and Delays

Wilmington Metro's real-time service alert system gives riders, planners, and transit administrators immediate access to disruption information across all active lines and stations. This page covers how alerts are defined, how the notification system operates, the most common disruption scenarios riders encounter, and the thresholds that determine how a service condition is classified and communicated. Understanding the alert framework helps riders make faster route decisions and sets expectations for response timelines.

Definition and scope

A real-time service alert is a machine-readable or human-readable notification triggered by an active condition that affects scheduled transit service. Alerts fall under two broad categories recognized across United States public transit systems: service advisories and service alerts. The Federal Transit Administration (FTA), which oversees public transit funding and compliance under 49 U.S.C. § 5307, distinguishes between planned disruptions communicated in advance and unplanned disruptions requiring immediate public notification.

For Wilmington Metro, the alert scope covers all routes and lines, all passenger stations, weekend service windows, and accessibility services including lift equipment and accessible boarding zones. Alerts related to paratransit options are issued through a parallel notification channel, as paratransit riders often have fixed trips that require advance rescheduling rather than spontaneous rerouting.

The Wilmington Metro home page provides the primary entry point to live alert feeds. Real-time alert data for US transit systems is commonly published using the General Transit Feed Specification Realtime (GTFS-RT) standard, maintained by Google and formally adopted by the FTA as the preferred open format for machine-readable transit data (FTA GTFS-RT guidance).

How it works

The alert pipeline moves through 4 sequential stages from detection to delivery:

1. Detection — Operations control staff or automated vehicle monitoring systems identify a service condition. Automated detection can flag a train or bus that deviates more than a set threshold — typically 3 minutes off scheduled headway — from its assigned pattern.
2. Classification — The condition is assigned a severity level. Minor delays under 5 minutes generally do not trigger a public alert; delays of 5 minutes or more, route diversions, station closures, and elevator outages each carry distinct classification codes under the GTFS-RT alert entity type.
3. Publication — Classified alerts are pushed to the GTFS-RT feed, the agency's mobile application, digital signs at affected stations, and SMS/email subscriber lists. The FTA's Transit Emergency Management guidelines recommend a public notification window of no more than 10 minutes from confirmation of a major service disruption.
4. Closure — When service is restored, an all-clear notification cancels the active alert. The alert record is retained in the historical feed log, which supports safety and security reviews and capital projects planning.

Advisory vs. Alert — a direct comparison:

Common scenarios

The disruption scenarios that generate the highest alert volume across US urban transit systems fall into 3 categories, each with distinct rider impact profiles.

Mechanical or vehicle failure — A single vehicle breakdown on a shared corridor can cascade into a 10–20 minute delay for trailing vehicles. Alerts for this scenario typically include an estimated restoration time and an alternate route recommendation drawn from schedules and hours data.

Infrastructure outage — Elevator and escalator failures at stations are among the most time-sensitive alerts for riders with mobility limitations. The Americans with Disabilities Act (ADA), enforced for transit under 49 CFR Part 37, requires transit agencies to notify riders of accessibility equipment outages. These alerts directly affect decisions about using accessibility services and parking at stations.

Weather and external events — Ice accumulation, flooding, and law enforcement activity can trigger both route diversions and full station suspensions. Weather-related alerts frequently reference the National Weather Service (weather.gov) forecast zone as part of the disruption context.

Decision boundaries

Not every operational anomaly qualifies as a public alert. The thresholds that determine whether a condition triggers notification generally follow these decision rules:

• Delay under 3 minutes: Absorbed into normal schedule variance; no alert issued.
• Delay of 3–5 minutes: Logged internally; may trigger an advisory update to the GTFS-RT feed without a push notification.
• Delay exceeding 5 minutes, or route diversion: Triggers a full public alert with affected stop identifiers, estimated delay duration, and alternate routing.
• Station or line suspension: Triggers the highest-severity alert class, activates staff at affected stations, and initiates coordination with safety and security personnel.
• Planned maintenance: Classified as a service advisory if notice is given at least 24 hours prior; reverts to a real-time alert classification if work overruns the planned window.

Riders enrolled in the SMS or email notification program receive alerts scoped to their saved routes. Unenrolled riders can access the live feed through the real-time alerts page or check frequently asked questions for guidance on configuring notifications. Incident reporting channels remain separate from the alert system and are used for safety-related passenger submissions rather than operational status updates.

References

• Federal Transit Administration — Urbanized Area Formula Grants (49 U.S.C. § 5307)
• FTA — General Transit Feed Specification (GTFS-RT)
• FTA — Emergency Preparedness and Planning
• eCFR 49 CFR Part 37 — Transportation Services for Individuals with Disabilities (ADA)
• National Weather Service — weather.gov