Network · data from 2026-11-12
AS264425 VAS Informática
Registry name: AS264425 - VASTELECOM E INFORMATICA LTDA ME, BR · PeeringDB
7IPv4 routes
100.0% RPKI valid · 14.3% with a route object
17IPv6 routes
100.0% RPKI valid · 5.9% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
22 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS264425, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS264425, 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.
| 131.221.186.0/23 | Valid | Nonecovered by 131.221.184.0/22 | 669 99% |
| 131.221.184.0/23 | Valid | Nonecovered by 131.221.184.0/22 | 668 99% |
| 2804:1e60::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:1000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:2000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:3000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:4000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:5000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:6000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:7000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:8000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:9000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:a000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:b000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:c000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:d000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:e000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 2804:1e60:f000::/36 | Valid | Nonecovered by 2804:1e60::/32 | 635 100% |
| 131.221.184.0/24 | Valid | Nonecovered by 131.221.184.0/22 | 207 31% |
| 131.221.187.0/24 | Valid | Nonecovered by 131.221.184.0/22 | 207 31% |
| 131.221.185.0/24 | Valid | Nonecovered by 131.221.184.0/22 | 206 31% |
| 131.221.186.0/24 | Valid | Nonecovered by 131.221.184.0/22 | 206 31% |
| 131.221.184.0/22 | Valid | Other IRR onlyBBOI, TC | 670 100% |
| 2804:1e60::/32 | Valid | Other IRR onlyBBOI, TC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS264425: AS-VASTELECOM. 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 (AS264425 isn't in the set, or no route object for AS264425 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.
| Name | Database | ASNs | Sets | AS264425 in it | Not covered |
|---|---|---|---|---|---|
| AS-VASTELECOM | BBOI | 1 | 1 | 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 24 are in fix.csv.
- Route object: none22
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 131.221.186.0/23 | No route object for it. A route object for 131.221.184.0/22 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 131.221.184.0/23 | No route object for it. A route object for 131.221.184.0/22 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:1000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:2000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:3000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:4000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:5000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:6000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:7000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:8000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:9000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:a000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:b000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:c000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:d000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:e000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 2804:1e60:f000::/36 | No route object for it. A route object for 2804:1e60::/32 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 131.221.184.0/24 | No route object for it. A route object for 131.221.184.0/22 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 131.221.187.0/24 | No route object for it. A route object for 131.221.184.0/22 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 131.221.185.0/24 | No route object for it. A route object for 131.221.184.0/22 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: none | 131.221.186.0/24 | No route object for it. A route object for 131.221.184.0/22 with origin AS264425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264425 in the RIR database for the space. |
| Route object: RIR | 131.221.184.0/22 | Route object only in BBOI, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1e60::/32 | Route object only in BBOI, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS264425 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.