bgpreport

Network · data from 2026-11-12

AS264492 TECHCOM PROVEDOR

Registry name: AS264492 - TECHCOM COMUNICACAO, COMERCIO E SERVICOS LTDA-ME, BR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
4Route objects not announced registered with origin AS264492, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264492, 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.
131.255.184.0/22 Valid Other IRR onlyRADB, TC 668 99% 67
131.255.184.0/23 Valid Other IRR onlyTC 668 99% 67
131.255.186.0/23 Valid Other IRR onlyTC 667 99% 67
2804:2078::/32 Valid Other IRR onlyRADB, TC 631 99% 70
2804:2078::/33 Valid Other IRR onlyTC 83 13% 32
2804:2078:8000::/33 Valid Other IRR onlyTC 83 13% 32

AS-SET

PeeringDB's irr_as_set for AS264492: AS264492:AS-SET. 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 (AS264492 isn't in the set, or no route object for AS264492 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 objectsAS264492 in itNot covered
AS264492:AS-SET In no IRR database read today.

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: RIR6
  • AS-SET: not found1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR131.255.184.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR131.255.184.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR131.255.186.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:2078::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2078::/33Route object only in TC. Add it in the RIR database for the space.83 of 636
Route object: RIR2804:2078:8000::/33Route object only in TC. Add it in the RIR database for the space.83 of 636
AS-SET: not foundAS264492:AS-SETPeeringDB names AS264492:AS-SET; no IRR database read has it.

Route objects not announced

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

131.255.184.0/24TCValid
131.255.185.0/24TCValid
131.255.186.0/24TCValid
131.255.187.0/24TCValid

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.