bgpreport

Network · data from 2026-11-12

AS262557 VIA SUL TELECOMUNICAÇOES

Registry name: AS262557 - VIA SUL TELECOMUNICACOES LTDA ME, BR · PeeringDB

29IPv4 routes 100.0% RPKI valid · 24.1% with a route object
7IPv6 routes 100.0% RPKI valid · 42.9% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 26 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS262557, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS262557, 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.

2804:64c::/34 Valid Nonecovered by 2804:64c::/33 636 100% 67
2804:64c:4000::/34 Valid Nonecovered by 2804:64c::/33 636 100% 67
2804:64c:8000::/34 Valid Nonecovered by 2804:64c:8000::/33 636 100% 67
2804:64c:c000::/34 Valid Nonecovered by 2804:64c:8000::/33 636 100% 67
168.0.104.0/23 Valid Nonecovered by 168.0.104.0/22 211 31% 57
168.0.106.0/23 Valid Nonecovered by 168.0.104.0/22 211 31% 57
177.73.240.0/23 Valid Nonecovered by 177.73.240.0/22 211 31% 57
177.73.242.0/23 Valid Nonecovered by 177.73.240.0/22 211 31% 57
177.73.244.0/23 Valid Nonecovered by 177.73.244.0/22 211 31% 57
177.73.246.0/23 Valid Nonecovered by 177.73.244.0/22 211 31% 57
168.0.104.0/24 Valid Nonecovered by 168.0.104.0/22 203 30% 56
168.0.105.0/24 Valid Nonecovered by 168.0.104.0/22 203 30% 56
168.0.106.0/24 Valid Nonecovered by 168.0.104.0/22 203 30% 56
168.0.107.0/24 Valid Nonecovered by 168.0.104.0/22 203 30% 56
177.73.240.0/24 Valid Nonecovered by 177.73.240.0/22 203 30% 56
177.73.241.0/24 Valid Nonecovered by 177.73.240.0/22 203 30% 56
177.73.242.0/24 Valid Nonecovered by 177.73.240.0/22 203 30% 56
177.73.243.0/24 Valid Nonecovered by 177.73.240.0/22 203 30% 56
177.73.245.0/24 Valid Nonecovered by 177.73.244.0/22 203 30% 56
177.73.246.0/24 Valid Nonecovered by 177.73.244.0/22 203 30% 56
177.73.247.0/24 Valid Nonecovered by 177.73.244.0/22 203 30% 56
201.148.240.0/24 Valid Nonecovered by 201.148.240.0/23 203 30% 56
201.148.241.0/24 Valid Nonecovered by 201.148.240.0/23 203 30% 56
201.148.242.0/24 Valid Nonecovered by 201.148.242.0/23 203 30% 56
201.148.243.0/24 Valid Nonecovered by 201.148.242.0/23 203 30% 56
177.73.244.0/24 Valid Nonecovered by 177.73.244.0/22 202 30% 56
177.73.240.0/21 Valid Other IRR onlyRADB, TC 672 100% 67
177.73.240.0/22 Valid Other IRR onlyRADB 672 100% 67
168.0.104.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
177.73.244.0/22 Valid Other IRR onlyRADB 671 100% 67
201.148.240.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
2804:64c::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:64c::/33 Valid Other IRR onlyRADB 635 100% 67
2804:64c:8000::/33 Valid Other IRR onlyRADB 635 100% 67
201.148.240.0/23 Valid Other IRR onlyRADB 211 31% 57
201.148.242.0/23 Valid Other IRR onlyRADB 211 31% 57

AS-SET

PeeringDB's irr_as_set for AS262557: AS-VIASULTELECOMBR. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS262557 isn't in the set, or no route object for AS262557 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS262557 in itNot covered
AS-VIASULTELECOMBR TC 4141 Yes 0

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

  • Route object: none26
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
Route object: none2804:64c::/34No route object for it. A route object for 2804:64c::/33 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.636 of 636
Route object: none2804:64c:4000::/34No route object for it. A route object for 2804:64c::/33 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.636 of 636
Route object: none2804:64c:8000::/34No route object for it. A route object for 2804:64c:8000::/33 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.636 of 636
Route object: none2804:64c:c000::/34No route object for it. A route object for 2804:64c:8000::/33 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.636 of 636
Route object: none168.0.104.0/23No route object for it. A route object for 168.0.104.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.211 of 673
Route object: none168.0.106.0/23No route object for it. A route object for 168.0.104.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.211 of 673
Route object: none177.73.240.0/23No route object for it. A route object for 177.73.240.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.211 of 673
Route object: none177.73.242.0/23No route object for it. A route object for 177.73.240.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.211 of 673
Route object: none177.73.244.0/23No route object for it. A route object for 177.73.244.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.211 of 673
Route object: none177.73.246.0/23No route object for it. A route object for 177.73.244.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.211 of 673
Route object: none168.0.104.0/24No route object for it. A route object for 168.0.104.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none168.0.105.0/24No route object for it. A route object for 168.0.104.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none168.0.106.0/24No route object for it. A route object for 168.0.104.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none168.0.107.0/24No route object for it. A route object for 168.0.104.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none177.73.240.0/24No route object for it. A route object for 177.73.240.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none177.73.241.0/24No route object for it. A route object for 177.73.240.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none177.73.242.0/24No route object for it. A route object for 177.73.240.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none177.73.243.0/24No route object for it. A route object for 177.73.240.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none177.73.245.0/24No route object for it. A route object for 177.73.244.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none177.73.246.0/24No route object for it. A route object for 177.73.244.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none177.73.247.0/24No route object for it. A route object for 177.73.244.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none201.148.240.0/24No route object for it. A route object for 201.148.240.0/23 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none201.148.241.0/24No route object for it. A route object for 201.148.240.0/23 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none201.148.242.0/24No route object for it. A route object for 201.148.242.0/23 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none201.148.243.0/24No route object for it. A route object for 201.148.242.0/23 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.203 of 673
Route object: none177.73.244.0/24No route object for it. A route object for 177.73.244.0/22 with origin AS262557 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262557 in the RIR database for the space.202 of 673
Route object: RIR177.73.240.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.73.240.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.0.104.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.73.244.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR201.148.240.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:64c::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:64c::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:64c:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR201.148.240.0/23Route object only in RADB. Add it in the RIR database for the space.211 of 673
Route object: RIR201.148.242.0/23Route object only in RADB. Add it in the RIR database for the space.211 of 673

Route objects not announced

Every route object with origin AS262557 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.