bgpreport

Network · data from 2026-11-12

AS272423 MASTER WI-FI FIBAS SP

Registry name: AS272423 - MASTER WI-FI FIBAS SP LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272423, 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.189.48.0/24 No ROA Other origin only 2 0%low visibility 2
179.0.150.0/24 No ROA Other IRR onlyTC 672 100% 66
2804:80f4::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:80f4:4000::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:80f4:8000::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:80f4:c000::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:80f4::/32 No ROA Other IRR onlyTC 1 0%low visibility 1

AS-SET

AS272423'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.

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none45.189.48.0/24No ROA covers it. Add a ROA for AS272423, maxLength 24.2 of 673
Route object: none45.189.48.0/24Route objects for it name AS269568. Add a route object with origin AS272423 in the RIR database for the space.2 of 673
ROA: none179.0.150.0/24No ROA covers it. Add a ROA for AS272423, maxLength 24.672 of 673
Route object: RIR179.0.150.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:80f4::/34No ROA covers it. Add a ROA for AS272423, maxLength 34.635 of 636
Route object: RIR2804:80f4::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:80f4:4000::/34No ROA covers it. Add a ROA for AS272423, maxLength 34.635 of 636
Route object: RIR2804:80f4:4000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:80f4:8000::/34No ROA covers it. Add a ROA for AS272423, maxLength 34.635 of 636
Route object: RIR2804:80f4:8000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:80f4:c000::/34No ROA covers it. Add a ROA for AS272423, maxLength 34.635 of 636
Route object: RIR2804:80f4:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:80f4::/32No ROA covers it. Add a ROA for AS272423, maxLength 32.1 of 636
Route object: RIR2804:80f4::/32Route object only in TC. Add it in the RIR database for the space.1 of 636

Route objects not announced

Every route object with origin AS272423 is announced.

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.