Network · data from 2026-11-12
AS3333 RIPE NCC
Registry name: RIPE-NCC-AS Reseaux IP Europeens Network Coordination Centre (RIPE NCC), NL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3333, 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.
| 193.0.0.128/29 | Invalid: maxLength | Nonecovered by 193.0.0.0/21 | 1 0%low visibility |
| 2001:67c:2e8:fffe::/64 | Invalid: maxLength | Nonecovered by 2001:67c:2e8::/48 | 1 0%low visibility |
| 2a13:27c0::/44 | Valid | None | 2 0%low visibility |
| 193.0.0.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 193.0.10.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.0.12.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.0.18.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.0.20.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.0.22.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 2001:67c:2e8::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS3333: RIPE::AS-RIPENCC. 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 (AS3333 isn't in the set, or no route object for AS3333 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 | AS3333 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-RIPENCC | RIPE | 3 | 1 | Yes | 3 |
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 6 are in fix.csv.
- ROA: maxLength2
- Route object: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 193.0.0.128/29 | ROA 193.0.0.0/21 AS3333 has maxLength 21; the route is a /29. Raise the maxLength, or add a ROA for 193.0.0.128/29. |
| Route object: none | 193.0.0.128/29 | No route object for it. A route object for 193.0.0.0/21 with origin AS3333 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS3333 in the RIR database for the space. |
| ROA: maxLength | 2001:67c:2e8:fffe::/64 | ROA 2001:67c:2e8::/48 AS3333 has maxLength 48; the route is a /64. Raise the maxLength, or add a ROA for 2001:67c:2e8:fffe::/64. |
| Route object: none | 2001:67c:2e8:fffe::/64 | No route object for it. A route object for 2001:67c:2e8::/48 with origin AS3333 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS3333 in the RIR database for the space. |
| Route object: none | 2a13:27c0::/44 | No route object for it. Add a route object with origin AS3333 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS3333 whose prefix no peer sees AS3333 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:f2dc:89::/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.