Network · data from 2026-11-12
AS266197 IBL TELECOM
Registry name: AS266197 - IBL TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266197, 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.
| 2804:3c38:100::/40 | Invalid: maxLength | Nonecovered by 2804:3c38::/34 | 1 0%low visibility |
| 160.20.160.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 160.20.162.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 2804:3c38:8000::/33 | Valid | Other IRR onlyRADB | 631 99% |
| 2804:3c38:8000::/34 | Valid | Other IRR onlyRADB | 335 53% |
| 2804:3c38:c000::/34 | Valid | Other IRR onlyRADB | 335 53% |
| 160.20.160.0/23 | Valid | Other IRR onlyRADB | 40 6%low visibility |
| 160.20.161.0/24 | Valid | Other IRR onlyRADB | 40 6%low visibility |
AS-SET
PeeringDB's irr_as_set for AS266197: AS-IBLTELECOM. 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 (AS266197 isn't in the set, or no route object for AS266197 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 | AS266197 in it | Not covered |
|---|---|---|---|---|---|
| AS-IBLTELECOM | ALTDB | 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 17 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: RIR7
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2804:3c38:100::/40 | ROA 2804:3c38::/32 AS266197 has maxLength 34; the route is a /40. Raise the maxLength, or add a ROA for 2804:3c38:100::/40. |
| Route object: none | 2804:3c38:100::/40 | No route object for it. A route object for 2804:3c38::/34 with origin AS266197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266197 in the RIR database for the space. |
| Route object: RIR | 160.20.160.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 160.20.162.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3c38:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3c38:8000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3c38:c000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 160.20.160.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 160.20.161.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266197 whose prefix no peer sees AS266197 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 160.20.160.0/22 | ALTDB, RADB | Valid |
| 160.20.162.0/23 | RADB | Valid |
| 160.20.163.0/24 | RADB | Valid |
| 2804:29e8::/32 | RADB | No ROA |
| 2804:3c38::/32 | ALTDB, RADB | Valid |
| 2804:3c38::/33 | RADB | Valid |
| 2804:3c38::/34 | RADB | Valid |
| 2804:3c38:4000::/34 | RADB | Valid |
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.