Announced routes
Every prefix a peer of the route collectors sees with origin AS13045, 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.
| 185.178.212.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 193.47.100.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 45.156.124.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.156.125.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 45.156.126.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2a02:1065:1000::/36 | No ROA | RIR databaseRIPE | 636 100% |
| 2a0a:6a80::/29 | No ROA | RIR databaseRIPE | 635 100% |
| 2a0f:8380::/29 | No ROA | RIR databaseRIPE | 635 100% |
| 81.14.185.0/24 | Valid | Nonecovered by 81.14.128.0/17 | 1 0%low visibility |
| 81.14.128.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 89.182.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 89.183.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 185.93.136.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 192.109.36.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.254.18.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.8.104.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.59.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 2001:678:7d4::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:678:9d4::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2001:678:b10::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a02:560::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS13045: RIPE::AS-HTP. 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 (AS13045 isn't in the set, or no route object for AS13045 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 | AS13045 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-HTP | RIPE | 11 | 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 9 are in fix.csv.
- ROA: none8
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.178.212.0/22 | No ROA covers it. Add a ROA for AS13045, maxLength 22. |
| ROA: none | 193.47.100.0/24 | No ROA covers it. Add a ROA for AS13045, maxLength 24. |
| ROA: none | 45.156.124.0/24 | No ROA covers it. Add a ROA for AS13045, maxLength 24. |
| ROA: none | 45.156.125.0/24 | No ROA covers it. Add a ROA for AS13045, maxLength 24. |
| ROA: none | 45.156.126.0/24 | No ROA covers it. Add a ROA for AS13045, maxLength 24. |
| ROA: none | 2a02:1065:1000::/36 | No ROA covers it. Add a ROA for AS13045, maxLength 36. |
| ROA: none | 2a0a:6a80::/29 | No ROA covers it. Add a ROA for AS13045, maxLength 29. |
| ROA: none | 2a0f:8380::/29 | No ROA covers it. Add a ROA for AS13045, maxLength 29. |
| Route object: none | 81.14.185.0/24 | No route object for it. A route object for 81.14.128.0/17 with origin AS13045 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13045 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS13045 is announced.
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.