bgpreport

Network · data from 2026-11-12

AS267502 SSNet Provedor

Registry name: AS267502 - VEM DIGITAL, BR · PeeringDB

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

Announced routes

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

190.89.220.0/24 Valid Nonecovered by 190.89.220.0/22 671 100% 66
190.89.222.0/24 Valid Nonecovered by 190.89.220.0/22 671 100% 67
190.89.223.0/24 Valid Nonecovered by 190.89.220.0/22 669 99% 66
190.89.221.0/24 Valid Nonecovered by 190.89.220.0/22 668 99% 66
190.89.222.0/23 Valid Nonecovered by 190.89.220.0/22 2 0%low visibility 2
201.182.70.0/23 Valid Other IRR onlyTC 672 100% 67
201.182.70.0/24 Valid Other IRR onlyTC 672 100% 67
201.182.71.0/24 Valid Other IRR onlyTC 672 100% 67
201.182.68.0/23 Valid Other IRR onlyTC 671 100% 66
201.182.68.0/24 Valid Other IRR onlyTC 671 100% 66
201.182.69.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
2804:4278::/33 Valid Other IRR onlyTC 635 100% 69
2804:4278:8000::/33 Valid Other IRR onlyTC 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS267502: AS267502:AS-SSNETPROVEDOR. 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 (AS267502 isn't in the set, or no route object for AS267502 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 objectsAS267502 in itNot covered
AS267502:AS-SSNETPROVEDOR TC 1328 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 33 are in fix.csv.

  • Route object: none5
  • Route object: RIR8
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
Route object: none190.89.220.0/24No route object for it. A route object for 190.89.220.0/22 with origin AS267502 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267502 in the RIR database for the space.671 of 673
Route object: none190.89.222.0/24No route object for it. A route object for 190.89.220.0/22 with origin AS267502 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267502 in the RIR database for the space.671 of 673
Route object: none190.89.223.0/24No route object for it. A route object for 190.89.220.0/22 with origin AS267502 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267502 in the RIR database for the space.669 of 673
Route object: none190.89.221.0/24No route object for it. A route object for 190.89.220.0/22 with origin AS267502 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267502 in the RIR database for the space.668 of 673
Route object: none190.89.222.0/23No route object for it. A route object for 190.89.220.0/22 with origin AS267502 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267502 in the RIR database for the space.2 of 673
Route object: RIR201.182.70.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR201.182.70.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR201.182.71.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR201.182.68.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR201.182.68.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR201.182.69.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:4278::/33Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:4278:8000::/33Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

131.196.20.0/22RADBNo ROA
190.89.220.0/22RADBValid
201.182.68.0/22RADB, TCValid
2804:4278::/32RADB, TCValid
2804:4278::/36TCValid
2804:4278:1000::/36TCValid
2804:4278:2000::/36TCValid
2804:4278:3000::/36TCValid
2804:4278:4000::/36TCValid
2804:4278:5000::/36TCValid
2804:4278:6000::/36TCValid
2804:4278:7000::/36TCValid
2804:4278:8000::/36TCValid
2804:4278:9000::/36TCValid
2804:4278:a000::/36TCValid
2804:4278:b000::/36TCValid
2804:4278:c000::/36TCValid
2804:4278:d000::/36TCValid
2804:4278:e000::/36TCValid
2804:4278:f000::/36TCValid

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.