bgpreport

Network · data from 2026-11-12

AS271033 FLAY NET TELECOM

Registry name: AS271033 - FLAY NET TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271033, 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.
187.84.125.0/24 No ROA Other IRR onlyRADB 671 100% 67
187.84.126.0/24 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
187.84.124.0/24 Valid Other IRR onlyRADB 671 100% 67
187.84.127.0/24 Valid Other IRR onlyRADB, TC 670 100% 67

AS-SET

AS271033'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 39 are in fix.csv.

  • ROA: none1
  • Route object: RIR4
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
ROA: none187.84.125.0/24No ROA covers it. Add a ROA for AS271033, maxLength 24.671 of 673
Route object: RIR187.84.125.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.84.126.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.84.124.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.84.127.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

187.84.124.0/22ALTDB, RADB, TCNo ROA
187.84.124.0/23RADBNo ROA
187.84.126.0/23RADBNo ROA
2804:753c::/32ALTDB, RADB, TCNo ROA
2804:753c::/33RADBNo ROA
2804:753c::/34RADBNo ROA
2804:753c::/35RADBNo ROA
2804:753c::/36RADBNo ROA
2804:753c:1000::/36RADBNo ROA
2804:753c:2000::/35RADBNo ROA
2804:753c:2000::/36RADBNo ROA
2804:753c:3000::/36RADBNo ROA
2804:753c:4000::/34RADBNo ROA
2804:753c:4000::/35RADBNo ROA
2804:753c:4000::/36RADBNo ROA
2804:753c:5000::/36RADBNo ROA
2804:753c:6000::/35RADBNo ROA
2804:753c:6000::/36RADBNo ROA
2804:753c:7000::/36RADBNo ROA
2804:753c:8000::/33RADBNo ROA
2804:753c:8000::/34RADBNo ROA
2804:753c:8000::/35RADBNo ROA
2804:753c:8000::/36RADBNo ROA
2804:753c:9000::/36RADBNo ROA
2804:753c:a000::/35RADBNo ROA
2804:753c:a000::/36RADBNo ROA
2804:753c:b000::/36RADBNo ROA
2804:753c:c000::/34RADBNo ROA
2804:753c:c000::/35RADBNo ROA
2804:753c:c000::/36RADBNo ROA
2804:753c:d000::/36RADBNo ROA
2804:753c:e000::/35RADBNo ROA
2804:753c:e000::/36RADBNo ROA
2804:753c:f000::/36RADBNo ROA

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.