Network · data from 2026-11-12
AS400942 AS-4E5A - 617A Corporation
Registry name: AS-4E5A - 617A Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS400942, 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.
| 2602:fcc3::/48 | Invalid: origin | Other origin only | 1 0%low visibility |
| 44.30.189.0/24 | No ROA | Other IRR onlyRADB | 668 99% |
AS-SET
AS400942 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 5 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2602:fcc3::/48 | ROAs covering it name AS399135, not AS400942. If AS400942 should announce it, add a ROA for AS400942. |
| Route object: none | 2602:fcc3::/48 | Route objects for it name AS399135. Add a route object with origin AS400942 in the RIR database for the space. |
| ROA: none | 44.30.189.0/24 | No ROA covers it. Add a ROA for AS400942, maxLength 24. |
| Route object: RIR | 44.30.189.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS400942 whose prefix no peer sees AS400942 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:fcc3:4e5::/48 | ARIN | Valid |
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.