bgpreport

Network · data from 2026-11-12

AS264566 INTERNET O SUL COMÉRCIO E SERVIÇOS

Registry name: AS264566 - INTERNET O SUL TELECOM LTDA., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264566, 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:21ac::/36 Valid Nonecovered by 2804:21ac::/33 14 2%low visibility 8
138.0.144.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
138.0.144.0/23 Valid Other IRR onlyRADB, TC 672 100% 67
138.0.146.0/23 Valid Other IRR onlyRADB, TC 672 100% 67
138.0.144.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
138.0.145.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
138.0.146.0/24 Valid Other IRR onlyRADB, TC 670 100% 67
138.0.147.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
2804:21ac::/33 Valid Other IRR onlyRADB, TC 636 100% 67
2804:21ac::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:21ac:8000::/33 Valid Other IRR onlyRADB, TC 6 1%low visibility 6
178.95.42.0/24 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS264566: AS264566:AS-ANNOUNCEMENTS. 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 (AS264566 isn't in the set, or no route object for AS264566 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 objectsAS264566 in itNot covered
AS264566:AS-ANNOUNCEMENTS TC 32155 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 11 are in fix.csv.

  • Route object: none1
  • Route object: RIR10
ChangePrefix or setDetailFull-table peers
Route object: none2804:21ac::/36No route object for it. A route object for 2804:21ac::/33 with origin AS264566 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264566 in the RIR database for the space.14 of 636
Route object: RIR138.0.144.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.0.144.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.0.146.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.0.144.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.0.145.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.0.146.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR138.0.147.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:21ac::/33Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:21ac::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:21ac:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.6 of 636

Route objects not announced

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