Network · data from 2026-11-12
AS25605 Cisco Security Cloud Operations
Registry name: SCANSAFE - Cisco OpenDNS, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25605, 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.
| 155.190.249.0/24 | Valid | None | 673 100% |
| 198.41.11.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 198.41.13.0/24 | Valid | Other IRR onlyRADB | 124 18% |
| 67.215.95.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
AS-SET
AS25605'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 28 are in fix.csv.
- Route object: none1
- Route object: RIR3
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 155.190.249.0/24 | No route object for it. Add a route object with origin AS25605 in the RIR database for the space. |
| Route object: RIR | 198.41.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.41.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 67.215.95.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25605 whose prefix no peer sees AS25605 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 108.171.134.0/24 | NTTCOM, RADB | No ROA |
| 108.171.141.0/24 | NTTCOM | No ROA |
| 108.171.142.0/24 | NTTCOM | No ROA |
| 108.171.143.0/24 | NTTCOM | No ROA |
| 127.50.127.0/24 | NTTCOM | No ROA |
| 150.208.129.0/24 | RADB | No ROA |
| 198.41.8.0/22 | RADB | Valid |
| 198.41.8.0/23 | RADB | Valid |
| 198.41.8.0/24 | RADB | Valid |
| 198.41.9.0/24 | RADB | Valid |
| 198.41.10.0/23 | RADB | Valid |
| 198.41.10.0/24 | RADB | Valid |
| 198.41.12.0/23 | RADB | Valid |
| 198.41.12.0/24 | RADB | Valid |
| 202.167.250.0/24 | NTTCOM | No ROA |
| 210.55.186.0/24 | RADB | No ROA |
| 210.55.200.0/24 | RADB | No ROA |
| 210.55.211.0/24 | RADB | No ROA |
| 2603:5000:90::/44 | ARIN | Invalid: origin |
| 2603:5000:3090::/44 | ARIN | Invalid: origin |
| 2603:5000:4090::/44 | ARIN | Invalid: origin |
| 2a00:9600:8700::/48 | RADB | No ROA |
| 2a00:9600:8710::/48 | NTTCOM | No ROA |
| 2a00:9600:8720::/48 | NTTCOM | No ROA |
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.