Announced routes
Every prefix a peer of the route collectors sees with origin AS62955, 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.
| 8.42.112.0/20 | No ROA | Other IRR onlyRADB | 669 99% |
| 8.45.64.0/20 | No ROA | Other IRR onlyRADB | 669 99% |
| 209.140.188.0/22 | No ROA | Other IRR onlyRADB | 669 99% |
| 216.113.188.0/22 | No ROA | Other IRR onlyRADB | 669 99% |
| 2620:0:57f::/48 | No ROA | Other IRR onlyRADB | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS62955: AS-EBAYMTBB. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS62955 isn't in the set, or no route object for AS62955 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS62955 in it | Not covered |
|---|---|---|---|---|---|
| AS-EBAYMTBB | RADB | 5 | 1 | Yes | 0 |
| RIPE (also) | 6 | 1 | Yes | 0 |
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 11 are in fix.csv.
- ROA: none5
- Route object: RIR5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 8.42.112.0/20 | No ROA covers it. Add a ROA for AS62955, maxLength 20. |
| Route object: RIR | 8.42.112.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 8.45.64.0/20 | No ROA covers it. Add a ROA for AS62955, maxLength 20. |
| Route object: RIR | 8.45.64.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 209.140.188.0/22 | No ROA covers it. Add a ROA for AS62955, maxLength 22. |
| Route object: RIR | 209.140.188.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 216.113.188.0/22 | No ROA covers it. Add a ROA for AS62955, maxLength 22. |
| Route object: RIR | 216.113.188.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2620:0:57f::/48 | No ROA covers it. Add a ROA for AS62955, maxLength 48. |
| Route object: RIR | 2620:0:57f::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS62955 whose prefix no peer sees AS62955 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 209.140.184.0/24 | RADB | No ROA |
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.