Network · data from 2026-11-12
AS262999 IVI TECNOLOGIA E COMUNICAO LTDA
Registry name: AS262999 - IVI TECNOLOGIA E COMUNICACAO LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262999, 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.
| 186.226.176.0/21 | No ROA | Nonecovered by 186.226.176.0/20 | 32 5%low visibility |
| 186.226.184.0/21 | No ROA | Nonecovered by 186.226.176.0/20 | 32 5%low visibility |
| 2804:9e0::/33 | No ROA | Nonecovered by 2804:9e0::/32 | 26 4%low visibility |
| 2804:9e0:8000::/33 | No ROA | Nonecovered by 2804:9e0::/32 | 26 4%low visibility |
| 186.226.176.0/20 | No ROA | Other IRR onlyRADB | 671 100% |
| 2804:9e0::/32 | No ROA | Other IRR onlyRADB | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS262999: AS-IVITELECOM. 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 (AS262999 isn't in the set, or no route object for AS262999 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 | AS262999 in it | Not covered |
|---|---|---|---|---|---|
| AS-IVITELECOM | RADB3 member sets in no database: AS-IVITELECOM-CLIENTS-DDOS, AS262769:AS-GEEKNET-BR, AS52872:AS-52872 | 183 | 8 | 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 15 are in fix.csv.
- ROA: none6
- Route object: none4
- Route object: RIR2
- AS-SET: missing member3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 186.226.176.0/21 | No ROA covers it. Add a ROA for AS262999, maxLength 21. |
| Route object: none | 186.226.176.0/21 | No route object for it. A route object for 186.226.176.0/20 with origin AS262999 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262999 in the RIR database for the space. |
| ROA: none | 186.226.184.0/21 | No ROA covers it. Add a ROA for AS262999, maxLength 21. |
| Route object: none | 186.226.184.0/21 | No route object for it. A route object for 186.226.176.0/20 with origin AS262999 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262999 in the RIR database for the space. |
| ROA: none | 2804:9e0::/33 | No ROA covers it. Add a ROA for AS262999, maxLength 33. |
| Route object: none | 2804:9e0::/33 | No route object for it. A route object for 2804:9e0::/32 with origin AS262999 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262999 in the RIR database for the space. |
| ROA: none | 2804:9e0:8000::/33 | No ROA covers it. Add a ROA for AS262999, maxLength 33. |
| Route object: none | 2804:9e0:8000::/33 | No route object for it. A route object for 2804:9e0::/32 with origin AS262999 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262999 in the RIR database for the space. |
| ROA: none | 186.226.176.0/20 | No ROA covers it. Add a ROA for AS262999, maxLength 20. |
| Route object: RIR | 186.226.176.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:9e0::/32 | No ROA covers it. Add a ROA for AS262999, maxLength 32. |
| Route object: RIR | 2804:9e0::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-IVITELECOM | AS-IVITELECOM (RADB) lists AS-IVITELECOM-CLIENTS-DDOS; no IRR database read has it. |
| AS-SET: missing member | AS-IVITELECOM | AS-IVITELECOM (RADB) lists AS262769:AS-GEEKNET-BR; no IRR database read has it. |
| AS-SET: missing member | AS-IVITELECOM | AS-IVITELECOM (RADB) lists AS52872:AS-52872; no IRR database read has it. |
Route objects not announced
Every route object with origin AS262999 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.