bgpreport

Network · data from 2026-11-12

AS268072 AS268072 - BNT TELECOM SERVICOS DE TELECOMUNICACOES LTDA

Registry name: AS268072 - BNT TELECOM SERVICOS DE TELECOMUNICACOES LTDA, 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
8Route objects not announced registered with origin AS268072, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268072, 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.168.224.0/22 Valid Other IRR onlyALTDB, RADB, TC 673 100% 67
45.168.227.0/24 Valid Other IRR onlyALTDB, TC 672 100% 66
45.168.226.0/24 Valid Other IRR onlyALTDB, TC 670 100% 67
2804:5790::/32 Valid Other IRR onlyALTDB, RADB, TC 636 100% 67
45.168.224.0/24 Valid Other IRR onlyALTDB, TC 204 30% 54
45.168.225.0/24 Valid Other IRR onlyALTDB, TC 203 30% 54

AS-SET

AS268072 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: RIR6
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR45.168.224.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.673 of 673
Route object: RIR45.168.227.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.168.226.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:5790::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR45.168.224.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.204 of 673
Route object: RIR45.168.225.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.203 of 673

Route objects not announced

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

45.168.224.0/23ALTDB, TCValid
45.168.226.0/23ALTDB, TCValid
2804:5790::/33TCValid
2804:5790::/34TCValid
2804:5790:4000::/34TCValid
2804:5790:8000::/33TCValid
2804:5790:8000::/34TCValid
2804:5790: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.