Network · data from 2026-11-12
AS262611 IVR PROVEDOR DE INTERNET LTDA
Registry name: AS262611 - Ivr informatica ltda me, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262611, 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.
| 168.228.168.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 168.228.168.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 168.228.170.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 168.228.171.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.176.0/21 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.176.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.176.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.177.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.178.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.178.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.180.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.180.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.181.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.182.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.85.182.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 168.228.168.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 168.228.169.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.85.176.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.85.179.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.85.180.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.85.183.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 168.228.170.0/24 | Valid | Other IRR onlyRADB, TC | 667 99% |
| 2804:2fc8::/33 | Valid | Other IRR onlyRADB, TC | 636 100% |
| 2804:2fc8:8000::/33 | Valid | Other IRR onlyRADB, TC | 636 100% |
| 2804:2fc8::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS262611: AS262611:AS-GLOBAL. 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 (AS262611 isn't in the set, or no route object for AS262611 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 | AS262611 in it | Not covered |
|---|---|---|---|---|---|
| AS262611:AS-GLOBAL | TC | 2 | 2 | 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 25 are in fix.csv.
- Route object: RIR25
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 168.228.168.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.168.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.170.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.171.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.176.0/21 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.176.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.176.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.177.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.178.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.178.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.180.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.180.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.181.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.182.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.182.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.168.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.169.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.176.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.179.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.180.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.85.183.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.228.170.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2fc8::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2fc8:8000::/33 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2fc8::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS262611 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.