Network · data from 2026-11-12
AS40919 FIDELITYEXPRESS - FIDELITY EXPRESS
Registry name: FIDELITYEXPRESS - FIDELITY EXPRESS, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40919, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 12.71.192.0/24 | Invalid: origin | None | 44 7%low visibility |
| 208.180.180.0/24 | No ROA | None | 673 100% |
AS-SET
AS40919 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 12.71.192.0/24 | ROAs covering it name AS7018, not AS40919. If AS40919 should announce it, add a ROA for AS40919. |
| Route object: none | 12.71.192.0/24 | No route object for it. Add a route object with origin AS40919 in the RIR database for the space. |
| ROA: none | 208.180.180.0/24 | No ROA covers it. Add a ROA for AS40919, maxLength 24. |
| Route object: none | 208.180.180.0/24 | No route object for it. Add a route object with origin AS40919 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS40919 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.