bgpreport

Network · data from 2026-11-12

AS264166 TURBO NET TELECOM LTDA

Registry name: AS264166 - TURBO NET TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264166, 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.
138.94.160.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 67
138.94.160.0/24 Valid Other IRR onlyRADB, TC 672 100% 67
138.94.161.0/24 Valid Other IRR onlyRADB, TC 672 100% 67
138.94.163.0/24 Valid Other IRR onlyRADB, TC 672 100% 67
138.94.162.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
2804:2380::/32 Valid Other IRR onlyALTDB, RADB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS264166: TC::AS264166:AS-ALL. 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 (AS264166 isn't in the set, or no route object for AS264166 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 objectsAS264166 in itNot covered
TC::AS264166:AS-ALL TC 119 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 9 are in fix.csv.

  • Route object: RIR6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR138.94.160.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.94.160.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.94.161.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.94.163.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.94.162.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:2380::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

138.94.160.0/23TCValid
138.94.162.0/23TCValid
2804:31e0::/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.