bgpreport

Network · data from 2026-11-12

AS263291 AS263291 - SAVNET TELECOMUNICACOES LTDA

Registry name: AS263291 - SAVNET TELECOMUNICACOES LTDA, BR · not in PeeringDB

9IPv4 routes 77.8% RPKI valid · 11.1% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
2RPKI invalid 0 origin · 2 maxLength
0No ROA 9 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS263291, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263291, 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.7.168.0/22 Invalid: maxLength Nonecovered by 201.7.168.0/21 1 0%low visibility 1
201.7.172.0/22 Invalid: maxLength Nonecovered by 201.7.168.0/21 1 0%low visibility 1
201.7.168.0/24 Valid Nonecovered by 201.7.168.0/21 669 99% 67
201.7.169.0/24 Valid Nonecovered by 201.7.168.0/21 669 99% 67
201.7.170.0/24 Valid Nonecovered by 201.7.168.0/21 669 99% 67
201.7.172.0/24 Valid Nonecovered by 201.7.168.0/21 669 99% 67
201.7.173.0/24 Valid Nonecovered by 201.7.168.0/21 669 99% 67
201.7.175.0/24 Valid Nonecovered by 201.7.168.0/21 669 99% 67
2804:168c:4000::/34 Valid Nonecovered by 2804:168c::/32 631 99% 67
201.7.168.0/21 Valid Other IRR onlyALTDB, RADB, TC 672 100% 67
2804:168c::/32 Valid Other IRR onlyALTDB, NTTCOM, TC 635 100% 67

AS-SET

AS263291 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 13 are in fix.csv.

  • ROA: maxLength2
  • Route object: none9
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: maxLength201.7.168.0/22ROA 201.7.168.0/21 AS263291 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 201.7.168.0/22.1 of 673
Route object: none201.7.168.0/22No route object for it. A route object for 201.7.168.0/21 with origin AS263291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263291 in the RIR database for the space.1 of 673
ROA: maxLength201.7.172.0/22ROA 201.7.168.0/21 AS263291 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 201.7.172.0/22.1 of 673
Route object: none201.7.172.0/22No route object for it. A route object for 201.7.168.0/21 with origin AS263291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263291 in the RIR database for the space.1 of 673
Route object: none201.7.168.0/24No route object for it. A route object for 201.7.168.0/21 with origin AS263291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263291 in the RIR database for the space.669 of 673
Route object: none201.7.169.0/24No route object for it. A route object for 201.7.168.0/21 with origin AS263291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263291 in the RIR database for the space.669 of 673
Route object: none201.7.170.0/24No route object for it. A route object for 201.7.168.0/21 with origin AS263291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263291 in the RIR database for the space.669 of 673
Route object: none201.7.172.0/24No route object for it. A route object for 201.7.168.0/21 with origin AS263291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263291 in the RIR database for the space.669 of 673
Route object: none201.7.173.0/24No route object for it. A route object for 201.7.168.0/21 with origin AS263291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263291 in the RIR database for the space.669 of 673
Route object: none201.7.175.0/24No route object for it. A route object for 201.7.168.0/21 with origin AS263291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263291 in the RIR database for the space.669 of 673
Route object: none2804:168c:4000::/34No route object for it. A route object for 2804:168c::/32 with origin AS263291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263291 in the RIR database for the space.631 of 636
Route object: RIR201.7.168.0/21Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:168c::/32Route object only in ALTDB, NTTCOM, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS263291 is announced.

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.