bgpreport

Network · data from 2026-11-12

AS265281 Tecbuy Telecomunicações LTDA.

Registry name: AS265281 - tecbuy telecomunicacoes ltda - me, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265281, 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.90.192.0/23 Valid Nonecovered by 168.90.192.0/22 671 100% 66
168.90.194.0/24 Valid Nonecovered by 168.90.192.0/22 671 100% 66
168.90.195.0/24 Valid Nonecovered by 168.90.192.0/22 671 100% 67
168.90.192.0/24 Valid Nonecovered by 168.90.192.0/22 198 29% 54
168.90.193.0/24 Valid Nonecovered by 168.90.192.0/22 198 29% 54
168.90.192.0/22 Valid Other IRR onlyRADB 671 100% 67
2804:2d6c::/32 Valid Other IRR onlyRADB 636 100% 67
2804:2d6c::/33 Valid Other IRR onlyRADB 346 54% 64
2804:2d6c:8000::/33 Valid Other IRR onlyRADB 346 54% 64

AS-SET

PeeringDB's irr_as_set for AS265281: TC::AS-TECBUY. 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 (AS265281 isn't in the set, or no route object for AS265281 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 objectsAS265281 in itNot covered
TC::AS-TECBUY TC 114 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: none5
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none168.90.192.0/23No route object for it. A route object for 168.90.192.0/22 with origin AS265281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265281 in the RIR database for the space.671 of 673
Route object: none168.90.194.0/24No route object for it. A route object for 168.90.192.0/22 with origin AS265281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265281 in the RIR database for the space.671 of 673
Route object: none168.90.195.0/24No route object for it. A route object for 168.90.192.0/22 with origin AS265281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265281 in the RIR database for the space.671 of 673
Route object: none168.90.192.0/24No route object for it. A route object for 168.90.192.0/22 with origin AS265281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265281 in the RIR database for the space.198 of 673
Route object: none168.90.193.0/24No route object for it. A route object for 168.90.192.0/22 with origin AS265281 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265281 in the RIR database for the space.198 of 673
Route object: RIR168.90.192.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:2d6c::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:2d6c::/33Route object only in RADB. Add it in the RIR database for the space.346 of 636
Route object: RIR2804:2d6c:8000::/33Route object only in RADB. Add it in the RIR database for the space.346 of 636

Route objects not announced

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