Network · data from 2026-11-12
AS200407 ASCartaya Telecable Cartaya S.L.
Registry name: ASCartaya Telecable Cartaya S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200407, 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.
| 195.5.94.0/24 | Invalid: origin | Other origin only | 10 1%low visibility |
AS-SET
AS200407 isn't in PeeringDB, where networks name their 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 7 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 195.5.94.0/24 | ROAs covering it name AS8903, AS12541, AS202766, not AS200407. If AS200407 should announce it, add a ROA for AS200407. |
| Route object: none | 195.5.94.0/24 | Route objects for it name AS8903. Add a route object with origin AS200407 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS200407 whose prefix no peer sees AS200407 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.90.52.0/22 | RIPE | Invalid: origin |
| 45.90.54.0/23 | RIPE | Invalid: origin |
| 45.90.54.0/24 | RIPE | Invalid: origin |
| 185.188.8.0/24 | RIPE | Invalid: origin |
| 185.249.208.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.