Announced routes
Every prefix a peer of the route collectors sees with origin AS41634, 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.
| 45.154.253.0/24 | No ROA | RIR databaseRIPE | 668 99% |
| 193.239.232.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 195.96.151.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2001:678:b30::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a12:1e01::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS41634: AS-SVEA. 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 (AS41634 isn't in the set, or no route object for AS41634 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 | AS41634 in it | Not covered |
|---|---|---|---|---|---|
| AS-SVEA | RIPE | 4 | 2 | 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 2 are in fix.csv.
- ROA: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.154.253.0/24 | No ROA covers it. Add a ROA for AS41634, maxLength 24. |
Route objects not announced
Route objects with origin AS41634 whose prefix no peer sees AS41634 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.22.170.0/24 | RIPE | Invalid: origin |
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.