bgpreport

Network · data from 2026-11-12

AS267374 AS267374 - ICOS TELECOM LTDA - ME

Registry name: AS267374 - ICOS TELECOM LTDA - ME, BR · not in 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
2Route objects not announced registered with origin AS267374, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267374, 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.
45.234.126.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 67
45.234.127.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 67
45.234.124.0/23 Valid Other IRR onlyALTDB, RADB 667 99% 67
45.234.124.0/24 Valid Other IRR onlyALTDB, RADB 666 99% 67
45.234.125.0/24 Valid Other IRR onlyALTDB, RADB 666 99% 67
2804:4c80::/32 Valid Other IRR onlyALTDB, RADB 632 99% 67

AS-SET

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

  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR45.234.126.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.234.127.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.234.124.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR45.234.124.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR45.234.125.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:4c80::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

45.234.124.0/22ALTDB, NTTCOM, RADBValid
45.234.126.0/23ALTDB, RADBValid

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.