bgpreport

Network · data from 2026-11-12

AS273855 AS273855 - CAIZA ELBAY SUSANA IVETH

Registry name: AS273855 - CAIZA ELBAY SUSANA IVETH, EC · not in PeeringDB

0IPv4 routes
5IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS273855, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273855, 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.
2803:9550:1::/48 No ROA Nonecovered by 2803:9550::/32 636 100% 67
2803:9550:2::/48 No ROA Nonecovered by 2803:9550::/32 636 100% 67
2803:9550:3::/48 No ROA Nonecovered by 2803:9550::/32 636 100% 67
2803:9550:4::/48 No ROA Nonecovered by 2803:9550::/32 636 100% 67
2803:9550:100::/40 No ROA Nonecovered by 2803:9550::/32 636 100% 67

AS-SET

AS273855 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2803:9550:1::/48No ROA covers it. Add a ROA for AS273855, maxLength 48.636 of 636
Route object: none2803:9550:1::/48No route object for it. A route object for 2803:9550::/32 with origin AS273855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273855 in the RIR database for the space.636 of 636
ROA: none2803:9550:2::/48No ROA covers it. Add a ROA for AS273855, maxLength 48.636 of 636
Route object: none2803:9550:2::/48No route object for it. A route object for 2803:9550::/32 with origin AS273855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273855 in the RIR database for the space.636 of 636
ROA: none2803:9550:3::/48No ROA covers it. Add a ROA for AS273855, maxLength 48.636 of 636
Route object: none2803:9550:3::/48No route object for it. A route object for 2803:9550::/32 with origin AS273855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273855 in the RIR database for the space.636 of 636
ROA: none2803:9550:4::/48No ROA covers it. Add a ROA for AS273855, maxLength 48.636 of 636
Route object: none2803:9550:4::/48No route object for it. A route object for 2803:9550::/32 with origin AS273855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273855 in the RIR database for the space.636 of 636
ROA: none2803:9550:100::/40No ROA covers it. Add a ROA for AS273855, maxLength 40.636 of 636
Route object: none2803:9550:100::/40No route object for it. A route object for 2803:9550::/32 with origin AS273855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273855 in the RIR database for the space.636 of 636

Route objects not announced

Route objects with origin AS273855 whose prefix no peer sees AS273855 announce. Many are kept on purpose (backup routes, space announced only in some places).

2803:9550::/32RADBNo 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.