bgpreport

Network · data from 2026-11-12

AS271266 AS271266 - CelNets Telecom Fiber

Registry name: AS271266 - CelNets Telecom Fiber, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271266, 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.
201.222.36.0/24 No ROA Other origin onlycovered by 201.222.36.0/22 672 100% 67
201.222.37.0/24 No ROA Nonecovered by 201.222.36.0/22 668 99% 67
201.222.38.0/24 No ROA Nonecovered by 201.222.36.0/22 668 99% 67
201.222.39.0/24 No ROA Nonecovered by 201.222.36.0/22 668 99% 67
201.222.36.0/22 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS271266 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: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none201.222.36.0/24No ROA covers it. Add a ROA for AS271266, maxLength 24.672 of 673
Route object: none201.222.36.0/24Route objects for it name AS271277. A route object for 201.222.36.0/22 with origin AS271266 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271266 in the RIR database for the space.672 of 673
ROA: none201.222.37.0/24No ROA covers it. Add a ROA for AS271266, maxLength 24.668 of 673
Route object: none201.222.37.0/24No route object for it. A route object for 201.222.36.0/22 with origin AS271266 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271266 in the RIR database for the space.668 of 673
ROA: none201.222.38.0/24No ROA covers it. Add a ROA for AS271266, maxLength 24.668 of 673
Route object: none201.222.38.0/24No route object for it. A route object for 201.222.36.0/22 with origin AS271266 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271266 in the RIR database for the space.668 of 673
ROA: none201.222.39.0/24No ROA covers it. Add a ROA for AS271266, maxLength 24.668 of 673
Route object: none201.222.39.0/24No route object for it. A route object for 201.222.36.0/22 with origin AS271266 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271266 in the RIR database for the space.668 of 673
ROA: none201.222.36.0/22No ROA covers it. Add a ROA for AS271266, maxLength 22.672 of 673
Route object: RIR201.222.36.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

2804:78cc::/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.