bgpreport

Network · data from 2026-11-12

AS270541 Planet Fiber

Registry name: AS270541 - Planet Fiber, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270541, 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.
177.124.152.0/23 Valid Nonecovered by 177.124.152.0/22 121 18% 41
177.124.154.0/23 Valid Nonecovered by 177.124.152.0/22 121 18% 41
2804:6d90::/33 Valid Nonecovered by 2804:6d90::/32 116 18% 43
2804:6d90:8000::/33 Valid Nonecovered by 2804:6d90::/32 116 18% 43
177.124.152.0/22 Valid Other IRR onlyTC 671 100% 66
2804:6d90::/32 Valid Other IRR onlyTC 636 100% 67

AS-SET

AS270541'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: none4
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none177.124.152.0/23No route object for it. A route object for 177.124.152.0/22 with origin AS270541 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270541 in the RIR database for the space.121 of 673
Route object: none177.124.154.0/23No route object for it. A route object for 177.124.152.0/22 with origin AS270541 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270541 in the RIR database for the space.121 of 673
Route object: none2804:6d90::/33No route object for it. A route object for 2804:6d90::/32 with origin AS270541 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270541 in the RIR database for the space.116 of 636
Route object: none2804:6d90:8000::/33No route object for it. A route object for 2804:6d90::/32 with origin AS270541 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270541 in the RIR database for the space.116 of 636
Route object: RIR177.124.152.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:6d90::/32Route object only in TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

177.124.152.0/24TCValid
177.124.153.0/24TCValid
177.124.154.0/24TCValid
177.124.155.0/24TCValid
2804:6d90::/34TCValid
2804:6d90:4000::/34TCValid
2804:6d90:8000::/34TCValid
2804:6d90: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.