Announced routes
Every prefix a peer of the route collectors sees with origin AS46733, 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.
| 153.76.7.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 23.165.136.0/24 | Valid | RIR databaseARIN | 670 100% |
| 204.209.34.0/24 | Valid | RIR databaseARIN | 670 100% |
| 2602:f9f4::/48 | Valid | RIR databaseARIN | 635 100% |
| 2602:f9f4:24::/48 | Valid | RIR databaseARIN | 632 99% |
| 2602:f9f4:25::/48 | Valid | RIR databaseARIN | 3 0%low visibility |
| 2602:f9f4:23::/48 | Valid | RIR databaseARIN | 2 0%low visibility |
| 2602:f9f4:26::/48 | Valid | RIR databaseARIN | 2 0%low visibility |
| 2602:f9f4:27::/48 | Valid | RIR databaseARIN | 2 0%low visibility |
| 2602:f9f4:21::/48 | Valid | RIR databaseARIN | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS46733: AS46733:AS-X6C. 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 (AS46733 isn't in the set, or no route object for AS46733 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 | AS46733 in it | Not covered |
|---|---|---|---|---|---|
| AS46733:AS-X6C | ARIN | 1 | 1 | Yes | 1 |
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 9 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 153.76.7.0/24 | ROAs covering it name AS16276, not AS46733. If AS46733 should announce it, add a ROA for AS46733. |
| Route object: none | 153.76.7.0/24 | Route objects for it name AS16276. Add a route object with origin AS46733 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS46733 whose prefix no peer sees AS46733 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:470:5b7::/48 | ARIN | Valid |
| 2602:f9f4:10::/48 | ARIN | Valid |
| 2602:f9f4:20::/48 | ARIN | Valid |
| 2602:f9f4:22::/48 | ARIN | Valid |
| 2602:f9f4:28::/48 | ARIN | Valid |
| 2602:f9f4:29::/48 | ARIN | Valid |
| 2602:f9f4:30::/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.