bgpreport

Network · data from 2026-11-12

AS266343 AS266343 - INFORLINK SERVICO DE COMUNICACAO MULTIMIDIA EIRELI

Registry name: AS266343 - INFORLINK SERVICO DE COMUNICACAO MULTIMIDIA EIRELI, BR · not in PeeringDB

7IPv4 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 AS266343, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266343, 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.
170.239.4.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
170.239.6.0/23 Valid Other IRR onlyTC 671 100% 67
170.239.6.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
170.239.4.0/22 Valid Other IRR onlyBBOI, NTTCOM, RADB, TC 666 99% 67
170.239.4.0/23 Valid Other IRR onlyTC 666 99% 67
170.239.5.0/24 Valid Other IRR onlyRADB, TC 664 99% 67
170.239.7.0/24 Valid Other IRR onlyRADB, TC 664 99% 67
2804:365c::/32 Valid Other IRR onlyBBOI, NTTCOM, RADB, TC 636 100% 67
2804:365c::/33 Valid Other IRR onlyTC 635 100% 67
2804:365c:8000::/33 Valid Other IRR onlyTC 635 100% 67

AS-SET

AS266343 isn't in PeeringDB, where networks name their AS-SET.

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 14 are in fix.csv.

  • Route object: RIR10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR170.239.4.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.239.6.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.239.6.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.239.4.0/22Route object only in BBOI, NTTCOM, RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR170.239.4.0/23Route object only in TC. Add it in the RIR database for the space.666 of 673
Route object: RIR170.239.5.0/24Route object only in RADB, TC. Add it in the RIR database for the space.664 of 673
Route object: RIR170.239.7.0/24Route object only in RADB, TC. Add it in the RIR database for the space.664 of 673
Route object: RIR2804:365c::/32Route object only in BBOI, NTTCOM, RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:365c::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:365c:8000::/33Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

2804:365c::/34TCValid
2804:365c:4000::/34TCValid
2804:365c:8000::/34TCValid
2804:365c:c000::/34TCValid

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.