bgpreport

Network · data from 2026-11-12

AS272727 AS272727 - FIBER BOX TELECOM

Registry name: AS272727 - FIBER BOX TELECOM, BR · not in PeeringDB

6IPv4 routes 100.0% RPKI valid · 0.0% with a route object
7IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 6 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS272727, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272727, 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.
190.12.152.0/23 Valid Nonecovered by 190.12.152.0/22 670 100% 66
190.12.153.0/24 Valid Nonecovered by 190.12.152.0/22 670 100% 66
190.12.154.0/23 Valid Nonecovered by 190.12.152.0/22 670 100% 66
190.12.154.0/24 Valid Nonecovered by 190.12.152.0/22 670 100% 66
190.12.155.0/24 Valid Nonecovered by 190.12.152.0/22 670 100% 66
190.12.152.0/24 Valid Nonecovered by 190.12.152.0/22 669 99% 66
2804:87b4::/33 Valid Other IRR onlyTC 634 100% 67
2804:87b4::/34 Valid Other IRR onlyTC 634 100% 67
2804:87b4:4000::/34 Valid Other IRR onlyTC 634 100% 67
2804:87b4:8000::/33 Valid Other IRR onlyTC 634 100% 67
2804:87b4:8000::/34 Valid Other IRR onlyTC 634 100% 67
2804:87b4:c000::/34 Valid Other IRR onlyTC 634 100% 67
2804:87b4::/32 Valid Other IRR onlyTC 2 0%low visibility 2

AS-SET

AS272727 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: none6
  • Route object: RIR7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none190.12.152.0/23No route object for it. A route object for 190.12.152.0/22 with origin AS272727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272727 in the RIR database for the space.670 of 673
Route object: none190.12.153.0/24No route object for it. A route object for 190.12.152.0/22 with origin AS272727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272727 in the RIR database for the space.670 of 673
Route object: none190.12.154.0/23No route object for it. A route object for 190.12.152.0/22 with origin AS272727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272727 in the RIR database for the space.670 of 673
Route object: none190.12.154.0/24No route object for it. A route object for 190.12.152.0/22 with origin AS272727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272727 in the RIR database for the space.670 of 673
Route object: none190.12.155.0/24No route object for it. A route object for 190.12.152.0/22 with origin AS272727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272727 in the RIR database for the space.670 of 673
Route object: none190.12.152.0/24No route object for it. A route object for 190.12.152.0/22 with origin AS272727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272727 in the RIR database for the space.669 of 673
Route object: RIR2804:87b4::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:87b4::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:87b4:4000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:87b4:8000::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:87b4:8000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:87b4:c000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:87b4::/32Route object only in TC. Add it in the RIR database for the space.2 of 636

Route objects not announced

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

190.12.152.0/22TCValid

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.