bgpreport

Network · data from 2026-11-12

AS264878 3T Telecom

Registry name: AS264878 - Innexa Tecnologias e Telecomunicacoes LTDA ME, BR · PeeringDB

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

Announced routes

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

168.227.122.0/24 No ROA Other IRR onlyRADB 672 100% 67
168.227.123.0/24 No ROA Other IRR onlyRADB 670 100% 66

AS-SET

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

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none168.227.122.0/24No ROA covers it. Add a ROA for AS264878, maxLength 24.672 of 673
Route object: RIR168.227.122.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none168.227.123.0/24No ROA covers it. Add a ROA for AS264878, maxLength 24.670 of 673
Route object: RIR168.227.123.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

168.227.120.0/22RADB, TCNo ROA
168.227.120.0/23RADB, TCNo ROA
168.227.120.0/24RADBNo ROA
168.227.121.0/24RADBNo ROA
168.227.122.0/23RADB, TCNo ROA
2804:2f38::/32RADB, TCNo ROA
2804:2f38::/33RADB, TCNo ROA
2804:2f38:8000::/33TCNo ROA
2804:32f8::/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.