bgpreport

Network · data from 2026-11-12

AS53127 VB Telecom Com. e Serv. de Info

Registry name: AS53127 - VB Telecom Com. e Serv. de Info Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53127, 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.110.128.0/22 Valid Nonecovered by 187.110.128.0/20 672 100% 67
187.110.128.0/23 Valid Nonecovered by 187.110.128.0/20 672 100% 67
187.110.130.0/23 Valid Nonecovered by 187.110.128.0/20 672 100% 67
187.110.132.0/24 Valid Nonecovered by 187.110.128.0/20 672 100% 67
187.110.138.0/23 Valid Nonecovered by 187.110.128.0/20 672 100% 67
187.110.140.0/23 Valid Nonecovered by 187.110.128.0/20 672 100% 67
187.110.132.0/22 Valid Nonecovered by 187.110.128.0/20 671 100% 67
187.110.132.0/23 Valid Nonecovered by 187.110.128.0/20 671 100% 67
187.110.134.0/23 Valid Nonecovered by 187.110.128.0/20 671 100% 67
187.110.136.0/21 Valid Nonecovered by 187.110.128.0/20 671 100% 67
187.110.136.0/22 Valid Nonecovered by 187.110.128.0/20 671 100% 67
187.110.136.0/23 Valid Nonecovered by 187.110.128.0/20 671 100% 67
187.110.140.0/22 Valid Nonecovered by 187.110.128.0/20 671 100% 67
187.110.131.0/24 Valid Nonecovered by 187.110.128.0/20 670 100% 67
187.110.133.0/24 Valid Nonecovered by 187.110.128.0/20 670 100% 67
187.110.134.0/24 Valid Nonecovered by 187.110.128.0/20 670 100% 67
187.110.135.0/24 Valid Nonecovered by 187.110.128.0/20 670 100% 67
187.110.142.0/23 Valid Nonecovered by 187.110.128.0/20 670 100% 67
187.110.128.0/20 Valid Other IRR onlyRADB 671 100% 67
2804:1ec::/32 Valid Other IRR onlyRADB 635 100% 68

AS-SET

PeeringDB's irr_as_set for AS53127: AS53127. 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 (AS53127 isn't in the set, or no route object for AS53127 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 objectsAS53127 in itNot covered
AS53127 A single AS number, not a set: AS53127 (this network), 2 route objects.

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

  • Route object: none18
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none187.110.128.0/22No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.672 of 673
Route object: none187.110.128.0/23No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.672 of 673
Route object: none187.110.130.0/23No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.672 of 673
Route object: none187.110.132.0/24No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.672 of 673
Route object: none187.110.138.0/23No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.672 of 673
Route object: none187.110.140.0/23No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.672 of 673
Route object: none187.110.132.0/22No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.671 of 673
Route object: none187.110.132.0/23No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.671 of 673
Route object: none187.110.134.0/23No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.671 of 673
Route object: none187.110.136.0/21No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.671 of 673
Route object: none187.110.136.0/22No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.671 of 673
Route object: none187.110.136.0/23No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.671 of 673
Route object: none187.110.140.0/22No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.671 of 673
Route object: none187.110.131.0/24No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.670 of 673
Route object: none187.110.133.0/24No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.670 of 673
Route object: none187.110.134.0/24No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.670 of 673
Route object: none187.110.135.0/24No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.670 of 673
Route object: none187.110.142.0/23No route object for it. A route object for 187.110.128.0/20 with origin AS53127 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53127 in the RIR database for the space.670 of 673
Route object: RIR187.110.128.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:1ec::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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