Network · data from 2026-11-12
AS262767 Avelino e Rodrigues
Registry name: AS262767 - Avelino e Rodrigues LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262767, 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.109.116.0/22 | No ROA | Other IRR onlyRADB | 672 100% |
| 187.109.116.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 187.109.123.0/24 | Valid | Other IRR onlyALTDB, RADB, TC | 672 100% |
| 187.109.119.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 2804:4f4::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 633 100% |
| 187.109.117.0/24 | Valid | Other IRR onlyRADB, TC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS262767: AS262767:AS-AVELINO. 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 (AS262767 isn't in the set, or no route object for AS262767 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 | AS262767 in it | Not covered |
|---|---|---|---|---|---|
| AS262767:AS-AVELINO | TC | 2 | 3 | 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 22 are in fix.csv.
- ROA: none1
- Route object: RIR6
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 187.109.116.0/22 | No ROA covers it. Add a ROA for AS262767, maxLength 22. |
| Route object: RIR | 187.109.116.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 187.109.116.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.109.123.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.109.119.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:4f4::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.109.117.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS262767 whose prefix no peer sees AS262767 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 186.227.64.0/20 | ALTDB, RADB | No ROA |
| 186.227.64.0/21 | ALTDB | No ROA |
| 186.227.72.0/21 | ALTDB | No ROA |
| 187.109.112.0/20 | ALTDB, RADB | No ROA |
| 187.109.116.0/23 | TC | Valid |
| 187.109.120.0/21 | ALTDB | No ROA |
| 187.109.120.0/22 | ALTDB | No ROA |
| 187.109.120.0/23 | ALTDB | No ROA |
| 187.109.122.0/23 | RADB, TC | No ROA |
| 187.109.122.0/24 | TC | No ROA |
| 187.109.124.0/22 | ALTDB | No ROA |
| 187.109.124.0/24 | ALTDB | No ROA |
| 187.109.125.0/24 | ALTDB | No ROA |
| 187.109.126.0/23 | ALTDB | No ROA |
| 2804:a54::/32 | RADB | No 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.