bgpreport

Network · data from 2026-11-12

AS267124 Rede Virtual Net

Registry name: AS267124 - Paulino Perreira Dos Santos Eireli, BR · PeeringDB

13IPv4 routes 53.8% RPKI valid · 53.8% with a route object
7IPv6 routes 100.0% RPKI valid · 28.6% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 11 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS267124, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267124, 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.230.222.0/24 No ROA Other origin only 671 100% 67
209.14.28.0/24 No ROA Nonecovered by 209.14.28.0/22 670 100% 67
209.14.29.0/24 No ROA Nonecovered by 209.14.28.0/22 670 100% 67
209.14.30.0/23 No ROA Nonecovered by 209.14.28.0/22 208 31% 56
209.14.30.0/24 No ROA Nonecovered by 209.14.28.0/22 208 31% 56
209.14.31.0/24 No ROA Nonecovered by 209.14.28.0/22 208 31% 56
2804:487c:700::/40 Valid Nonecovered by 2804:487c::/32 635 100% 67
2804:487c:800::/40 Valid Nonecovered by 2804:487c::/32 635 100% 67
2804:487c:900::/40 Valid Nonecovered by 2804:487c::/32 635 100% 67
2804:487c:fe00::/40 Valid Nonecovered by 2804:487c::/32 635 100% 67
2804:487c:ff00::/40 Valid Nonecovered by 2804:487c::/32 635 100% 67
45.229.52.0/24 Valid Other IRR onlyTC 672 100% 67
45.229.52.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
45.229.52.0/23 Valid Other IRR onlyTC 671 100% 66
45.229.54.0/23 Valid Other IRR onlyTC 671 100% 66
2804:487c::/32 Valid Other IRR onlyRADB, TC 632 99% 67
2804:487c:6000::/35 Valid Other IRR onlyRADB 632 99% 67
45.229.53.0/24 Valid Other IRR onlyTC 189 28% 52
45.229.54.0/24 Valid Other IRR onlyTC 187 28% 51
45.229.55.0/24 Valid Other IRR onlyTC 187 28% 51

AS-SET

PeeringDB's irr_as_set for AS267124: AS267124:AS-VIRTUAL-NET. 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 (AS267124 isn't in the set, or no route object for AS267124 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 objectsAS267124 in itNot covered
AS267124:AS-VIRTUAL-NET TC 1311 Yes 1

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

  • ROA: none6
  • Route object: none11
  • Route object: RIR9
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.230.222.0/24No ROA covers it. Add a ROA for AS267124, maxLength 24.671 of 673
Route object: none45.230.222.0/24Route objects for it name AS267184. Add a route object with origin AS267124 in the RIR database for the space.671 of 673
ROA: none209.14.28.0/24No ROA covers it. Add a ROA for AS267124, maxLength 24.670 of 673
Route object: none209.14.28.0/24No route object for it. A route object for 209.14.28.0/22 with origin AS267124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267124 in the RIR database for the space.670 of 673
ROA: none209.14.29.0/24No ROA covers it. Add a ROA for AS267124, maxLength 24.670 of 673
Route object: none209.14.29.0/24No route object for it. A route object for 209.14.28.0/22 with origin AS267124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267124 in the RIR database for the space.670 of 673
ROA: none209.14.30.0/23No ROA covers it. Add a ROA for AS267124, maxLength 23.208 of 673
Route object: none209.14.30.0/23No route object for it. A route object for 209.14.28.0/22 with origin AS267124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267124 in the RIR database for the space.208 of 673
ROA: none209.14.30.0/24No ROA covers it. Add a ROA for AS267124, maxLength 24.208 of 673
Route object: none209.14.30.0/24No route object for it. A route object for 209.14.28.0/22 with origin AS267124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267124 in the RIR database for the space.208 of 673
ROA: none209.14.31.0/24No ROA covers it. Add a ROA for AS267124, maxLength 24.208 of 673
Route object: none209.14.31.0/24No route object for it. A route object for 209.14.28.0/22 with origin AS267124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267124 in the RIR database for the space.208 of 673
Route object: none2804:487c:700::/40No route object for it. A route object for 2804:487c::/32 with origin AS267124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267124 in the RIR database for the space.635 of 636
Route object: none2804:487c:800::/40No route object for it. A route object for 2804:487c::/32 with origin AS267124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267124 in the RIR database for the space.635 of 636
Route object: none2804:487c:900::/40No route object for it. A route object for 2804:487c::/32 with origin AS267124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267124 in the RIR database for the space.635 of 636
Route object: none2804:487c:fe00::/40No route object for it. A route object for 2804:487c::/32 with origin AS267124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267124 in the RIR database for the space.635 of 636
Route object: none2804:487c:ff00::/40No route object for it. A route object for 2804:487c::/32 with origin AS267124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267124 in the RIR database for the space.635 of 636
Route object: RIR45.229.52.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.229.52.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.229.52.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.229.54.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:487c::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:487c:6000::/35Route object only in RADB. Add it in the RIR database for the space.632 of 636
Route object: RIR45.229.53.0/24Route object only in TC. Add it in the RIR database for the space.189 of 673
Route object: RIR45.229.54.0/24Route object only in TC. Add it in the RIR database for the space.187 of 673
Route object: RIR45.229.55.0/24Route object only in TC. Add it in the RIR database for the space.187 of 673

Route objects not announced

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

209.14.28.0/22RADBNo ROA
804:487c::/32RADBNo 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.