Announced routes
Every prefix a peer of the route collectors sees with origin AS61308, 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.
| 188.130.239.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 93.170.200.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 93.171.192.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 95.215.109.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.213.136.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 192.144.48.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 192.144.50.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 192.144.51.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 93.170.200.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.170.201.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.170.202.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.170.203.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.170.205.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.170.206.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.170.207.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.171.192.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.171.195.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.171.196.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.171.197.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.171.198.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 93.171.199.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 185.213.136.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 185.213.137.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 185.213.138.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 185.213.139.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
AS-SET
AS61308's PeeringDB record names no AS-SET.
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 13 are in fix.csv.
- ROA: none1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 188.130.239.0/24 | No ROA covers it. Add a ROA for AS61308, maxLength 24. |
Route objects not announced
Route objects with origin AS61308 whose prefix no peer sees AS61308 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 93.170.200.0/22 | RIPE | Valid |
| 93.170.204.0/22 | RIPE | Valid |
| 93.170.204.0/24 | RIPE | Valid |
| 93.171.192.0/22 | RIPE | Valid |
| 93.171.192.0/23 | RIPE | Valid |
| 93.171.193.0/24 | RIPE | Valid |
| 93.171.194.0/23 | RIPE | Valid |
| 93.171.194.0/24 | RIPE | Valid |
| 93.171.196.0/23 | RIPE | Valid |
| 93.171.198.0/23 | RIPE | Valid |
| 2001:67c:1188::/48 | RIPE | Valid |
| 2001:67c:1188:8000::/49 | RIPE | Invalid: maxLength |
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.