Network · data from 2026-11-12
AS265080 AD Telecom
Registry name: AS265080 - AD TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265080, 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.
| 45.180.35.0/24 | Invalid: origin | Other origin only | 48 7%low visibility |
| 2804:3278::/34 | Valid | Nonecovered by 2804:3278::/33 | 348 55% |
| 2804:3278:4000::/34 | Valid | Nonecovered by 2804:3278::/33 | 348 55% |
| 2804:3278:8000::/34 | Valid | Nonecovered by 2804:3278:8000::/33 | 348 55% |
| 2804:3278:c000::/34 | Valid | Nonecovered by 2804:3278:8000::/33 | 348 55% |
| 2804:3278::/48 | Valid | Nonecovered by 2804:3278::/33 | 347 55% |
| 2804:3278:4000::/48 | Valid | Nonecovered by 2804:3278::/33 | 320 50% |
| 2804:3278:12b::/48 | Valid | Nonecovered by 2804:3278::/33 | 2 0%low visibility |
| 2804:3278:141::/48 | Valid | Nonecovered by 2804:3278::/33 | 2 0%low visibility |
| 2804:3278:153::/48 | Valid | Nonecovered by 2804:3278::/33 | 2 0%low visibility |
| 2804:3278:154::/48 | Valid | Nonecovered by 2804:3278::/33 | 2 0%low visibility |
| 2804:3278:156::/48 | Valid | Nonecovered by 2804:3278::/33 | 2 0%low visibility |
| 170.233.120.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.233.120.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.233.120.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.233.122.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 170.233.122.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.233.123.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.233.121.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 2804:3278::/32 | Valid | Other IRR onlyRADB, TC | 632 99% |
| 2804:3278::/33 | Valid | Other IRR onlyRADB | 632 99% |
| 2804:3278:8000::/33 | Valid | Other IRR onlyRADB | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS265080: AS265080. 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 (AS265080 isn't in the set, or no route object for AS265080 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 | AS265080 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS265080 | A single AS number, not a set: AS265080 (this network), 11 route objects. | |||||
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.
- ROA: origin1
- Route object: none12
- Route object: RIR10
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 45.180.35.0/24 | ROAs covering it name AS269162, not AS265080. If AS265080 should announce it, add a ROA for AS265080. |
| Route object: none | 45.180.35.0/24 | Route objects for it name AS269162. Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278::/34 | No route object for it. A route object for 2804:3278::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278:4000::/34 | No route object for it. A route object for 2804:3278::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278:8000::/34 | No route object for it. A route object for 2804:3278:8000::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278:c000::/34 | No route object for it. A route object for 2804:3278:8000::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278::/48 | No route object for it. A route object for 2804:3278::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278:4000::/48 | No route object for it. A route object for 2804:3278::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278:12b::/48 | No route object for it. A route object for 2804:3278::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278:141::/48 | No route object for it. A route object for 2804:3278::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278:153::/48 | No route object for it. A route object for 2804:3278::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278:154::/48 | No route object for it. A route object for 2804:3278::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: none | 2804:3278:156::/48 | No route object for it. A route object for 2804:3278::/33 with origin AS265080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265080 in the RIR database for the space. |
| Route object: RIR | 170.233.120.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.233.120.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.233.120.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.233.122.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.233.122.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.233.123.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.233.121.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3278::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3278::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3278:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265080 whose prefix no peer sees AS265080 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.233.124.0/23 | 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.