bgpreport

Network · data from 2026-11-12

AS267957 Andys Informatica Com. e Serv. de Info.

Registry name: AS267957 - NITRO TELECOM, BR · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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 AS267957, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267957, 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.166.128.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
45.166.129.0/24 Valid Other IRR onlyTC 672 100% 67
45.166.131.0/24 Valid Other IRR onlyTC 672 100% 67
45.166.128.0/24 Valid Other IRR onlyTC 671 100% 67
45.166.130.0/24 Valid Other IRR onlyTC 671 100% 67
2804:55cc::/34 Valid Other IRR onlyTC 636 100% 67
2804:55cc:4000::/34 Valid Other IRR onlyTC 636 100% 67
2804:55cc:8000::/34 Valid Other IRR onlyTC 636 100% 67
2804:55cc:c000::/34 Valid Other IRR onlyTC 636 100% 67
2804:55cc::/32 Valid Other IRR onlyRADB, TC 635 100% 67

AS-SET

AS267957's PeeringDB record names no 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: RIR45.166.128.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.166.129.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.166.131.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.166.128.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.166.130.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:55cc::/34Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:55cc:4000::/34Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:55cc:8000::/34Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:55cc:c000::/34Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:55cc::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.166.128.0/23TCValid
45.166.130.0/23TCValid
2804:55cc::/33TCValid
2804:55cc:8000::/33TCValid

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.