bgpreport

Network · data from 2026-11-12

AS52814 NETPLAY TELECOM

Registry name: AS52814 - INTERNET PLAY LTDA, BR · PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.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 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
31Route objects not announced registered with origin AS52814, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS52814, 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.72.8.0/21 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
177.72.8.0/22 Valid Other IRR onlyRADB 667 99% 67
177.72.12.0/22 Valid Other IRR onlyRADB 667 99% 67
2804:45e8::/32 Valid Other IRR onlyALTDB, TC 634 100% 69
2804:45e8::/33 Valid Other IRR onlyRADB 632 99% 67
2804:45e8:8000::/33 Valid Other IRR onlyRADB 632 99% 67
2804:45e8::/34 Valid Other IRR onlyRADB 351 55% 65
2804:45e8:4000::/34 Valid Other IRR onlyRADB 351 55% 65
2804:45e8:8000::/34 Valid Other IRR onlyRADB 351 55% 65
2804:45e8:c000::/34 Valid Other IRR onlyRADB 351 55% 65
177.72.8.0/23 Valid Other IRR onlyRADB 205 30% 56
177.72.10.0/23 Valid Other IRR onlyRADB 205 30% 56
177.72.12.0/23 Valid Other IRR onlyRADB 205 30% 56
177.72.14.0/23 Valid Other IRR onlyRADB 205 30% 56
177.72.8.0/24 Valid Other IRR onlyRADB 0 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS52814: AS-NETPLAY-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS52814 isn't in the set, or no route object for AS52814 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS52814 in itNot covered
AS-NETPLAY-ALL In no IRR database read today.

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 47 are in fix.csv.

  • Route object: RIR15
  • AS-SET: not found1
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
Route object: RIR177.72.8.0/21Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.72.8.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.72.12.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:45e8::/32Route object only in ALTDB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:45e8::/33Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:45e8:8000::/33Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:45e8::/34Route object only in RADB. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:45e8:4000::/34Route object only in RADB. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:45e8:8000::/34Route object only in RADB. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:45e8:c000::/34Route object only in RADB. Add it in the RIR database for the space.351 of 636
Route object: RIR177.72.8.0/23Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.72.10.0/23Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.72.12.0/23Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.72.14.0/23Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.72.8.0/24Route object only in RADB. Add it in the RIR database for the space.0 of 673
AS-SET: not foundAS-NETPLAY-ALLPeeringDB names AS-NETPLAY-ALL; no IRR database read has it.

Route objects not announced

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

177.72.9.0/24RADBValid
177.72.10.0/24RADBValid
177.72.11.0/24RADBValid
177.72.12.0/24RADBValid
177.72.13.0/24RADBValid
177.72.14.0/24RADBValid
177.72.15.0/24RADBValid
2804:45e8::/35RADBValid
2804:45e8::/36RADBValid
2804:45e8:1000::/36RADBValid
2804:45e8:2000::/35RADBValid
2804:45e8:2000::/36RADBValid
2804:45e8:3000::/36RADBValid
2804:45e8:4000::/35RADBValid
2804:45e8:4000::/36RADBValid
2804:45e8:5000::/36RADBValid
2804:45e8:6000::/35RADBValid
2804:45e8:6000::/36RADBValid
2804:45e8:7000::/36RADBValid
2804:45e8:8000::/35RADBValid
2804:45e8:8000::/36RADBValid
2804:45e8:9000::/36RADBValid
2804:45e8:a000::/35RADBValid
2804:45e8:a000::/36RADBValid
2804:45e8:b000::/36RADBValid
2804:45e8:c000::/35RADBValid
2804:45e8:c000::/36RADBValid
2804:45e8:d000::/36RADBValid
2804:45e8:e000::/35RADBValid
2804:45e8:e000::/36RADBValid
2804:45e8:f000::/36RADBValid

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.