bgpreport

Network · data from 2026-11-12

AS53115 ISPX Solucoes em Telecomunicacoes

Registry name: AS53115 - ISPX Solucoes em Telecomunicacoes SPE Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53115, 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.

2804:4d48:1570::/48 Valid Nonecovered by 2804:4d48::/34 635 100% 67
2804:4d48:d100::/40 Valid Nonecovered by 2804:4d48:c000::/34 635 100% 67
2804:4d48:e001::/48 Valid Nonecovered by 2804:4d48:c000::/34 635 100% 67
2804:4d48:e003::/48 Valid Nonecovered by 2804:4d48:c000::/34 635 100% 67
2804:4d48:e004::/48 Valid Nonecovered by 2804:4d48:c000::/34 635 100% 67
2804:4d48:e005::/48 Valid Nonecovered by 2804:4d48:c000::/34 635 100% 67
2804:4d48:e007::/48 Valid Nonecovered by 2804:4d48:c000::/34 635 100% 67
2804:4d48:e010::/48 Valid Nonecovered by 2804:4d48:c000::/34 635 100% 67
2804:4d48:e011::/48 Valid Nonecovered by 2804:4d48:c000::/34 635 100% 67
2804:4d48:e012::/48 Valid Nonecovered by 2804:4d48:c000::/34 635 100% 67
187.109.202.0/23 Valid Nonecovered by 187.109.200.0/22 3 0%low visibility 3
187.109.192.0/20 Valid Other IRR onlyRADB, TC 671 100% 66
187.109.192.0/21 Valid Other IRR onlyRADB 671 100% 66
187.109.192.0/22 Valid Other IRR onlyRADB 671 100% 66
187.109.192.0/23 Valid Other IRR onlyRADB 671 100% 66
187.109.194.0/23 Valid Other IRR onlyRADB 671 100% 66
187.109.194.0/24 Valid Other IRR onlyRADB 671 100% 66
187.109.195.0/24 Valid Other IRR onlyRADB 671 100% 66
187.109.196.0/22 Valid Other IRR onlyRADB 671 100% 66
187.109.196.0/23 Valid Other IRR onlyRADB 671 100% 66
187.109.198.0/23 Valid Other IRR onlyRADB 671 100% 66
187.109.198.0/24 Valid Other IRR onlyRADB 671 100% 66
187.109.200.0/21 Valid Other IRR onlyRADB 671 100% 66
187.109.200.0/22 Valid Other IRR onlyRADB 671 100% 66
187.109.200.0/23 Valid Other IRR onlyRADB 671 100% 66
187.109.201.0/24 Valid Other IRR onlyRADB 671 100% 66
187.109.204.0/22 Valid Other IRR onlyRADB 671 100% 66
187.109.204.0/23 Valid Other IRR onlyRADB 671 100% 66
187.109.205.0/24 Valid Other IRR onlyRADB 671 100% 66
187.109.206.0/23 Valid Other IRR onlyRADB 671 100% 66
187.109.206.0/24 Valid Other IRR onlyRADB 671 100% 66
187.109.192.0/24 Valid Other IRR onlyRADB 670 100% 66
187.109.197.0/24 Valid Other IRR onlyRADB 670 100% 66
187.109.199.0/24 Valid Other IRR onlyRADB 670 100% 66
187.109.200.0/24 Valid Other IRR onlyRADB 670 100% 66
187.109.203.0/24 Valid Other IRR onlyRADB 670 100% 66
187.109.207.0/24 Valid Other IRR onlyRADB 670 100% 66
2804:4d48::/32 Valid Other IRR onlyRADB, TC 636 100% 67
2804:4d48::/33 Valid Other IRR onlyRADB 635 100% 67
2804:4d48::/34 Valid Other IRR onlyRADB 635 100% 67
2804:4d48:4000::/34 Valid Other IRR onlyRADB 635 100% 67
2804:4d48:8000::/33 Valid Other IRR onlyRADB 635 100% 67
2804:4d48:8000::/34 Valid Other IRR onlyRADB 635 100% 67
2804:4d48:c000::/34 Valid Other IRR onlyRADB 635 100% 67
187.109.204.0/24 Valid Other IRR onlyRADB 123 18% 44

AS-SET

PeeringDB's irr_as_set for AS53115: AS-53115:AS-CUSTOMERS. 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 (AS53115 isn't in the set, or no route object for AS53115 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 objectsAS53115 in itNot covered
AS-53115:AS-CUSTOMERS RADBlists itself further down1 member set in no database: AS264943:AS-52587 257103,440 Yes 0

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

  • Route object: none11
  • Route object: RIR34
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
Route object: none2804:4d48:1570::/48No route object for it. A route object for 2804:4d48::/34 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.635 of 636
Route object: none2804:4d48:d100::/40No route object for it. A route object for 2804:4d48:c000::/34 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.635 of 636
Route object: none2804:4d48:e001::/48No route object for it. A route object for 2804:4d48:c000::/34 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.635 of 636
Route object: none2804:4d48:e003::/48No route object for it. A route object for 2804:4d48:c000::/34 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.635 of 636
Route object: none2804:4d48:e004::/48No route object for it. A route object for 2804:4d48:c000::/34 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.635 of 636
Route object: none2804:4d48:e005::/48No route object for it. A route object for 2804:4d48:c000::/34 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.635 of 636
Route object: none2804:4d48:e007::/48No route object for it. A route object for 2804:4d48:c000::/34 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.635 of 636
Route object: none2804:4d48:e010::/48No route object for it. A route object for 2804:4d48:c000::/34 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.635 of 636
Route object: none2804:4d48:e011::/48No route object for it. A route object for 2804:4d48:c000::/34 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.635 of 636
Route object: none2804:4d48:e012::/48No route object for it. A route object for 2804:4d48:c000::/34 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.635 of 636
Route object: none187.109.202.0/23No route object for it. A route object for 187.109.200.0/22 with origin AS53115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53115 in the RIR database for the space.3 of 673
Route object: RIR187.109.192.0/20Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.192.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.192.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.192.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.194.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.194.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.195.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.196.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.196.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.198.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.198.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.200.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.200.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.200.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.201.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.204.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.204.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.205.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.206.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.206.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.109.192.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.109.197.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.109.199.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.109.200.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.109.203.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.109.207.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:4d48::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:4d48::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4d48::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4d48:4000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4d48:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4d48:8000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4d48:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR187.109.204.0/24Route object only in RADB. Add it in the RIR database for the space.123 of 673
AS-SET: missing memberAS-53115:AS-CUSTOMERSAS-53115:AS-CUSTOMERS (RADB) lists AS264943:AS-52587; no IRR database read has it.

Route objects not announced

Every route object with origin AS53115 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.