Network · data from 2026-11-12
AS29244 CETIN Bulgaria AS29244
Registry name: TelenorBG-AS CETIN Bulgaria EAD, BG · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29244, 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.
| 85.118.192.0/24 | Valid | Nonecovered by 85.118.192.0/21 | 673 100% |
| 85.118.196.0/24 | Valid | Nonecovered by 85.118.192.0/21 | 673 100% |
| 87.120.79.0/24 | Valid | Nonecovered by 87.120.72.0/21 | 673 100% |
| 91.92.8.0/24 | Valid | Nonecovered by 91.92.8.0/21 | 673 100% |
| 91.92.9.0/24 | Valid | Nonecovered by 91.92.8.0/21 | 673 100% |
| 91.92.10.0/24 | Valid | Nonecovered by 91.92.8.0/21 | 673 100% |
| 91.92.11.0/24 | Valid | Nonecovered by 91.92.8.0/21 | 673 100% |
| 91.92.12.0/24 | Valid | Nonecovered by 91.92.8.0/21 | 673 100% |
| 91.92.13.0/24 | Valid | Nonecovered by 91.92.8.0/21 | 673 100% |
| 91.92.14.0/24 | Valid | Nonecovered by 91.92.8.0/21 | 673 100% |
| 91.92.15.0/24 | Valid | Nonecovered by 91.92.8.0/21 | 673 100% |
| 85.118.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 93.123.88.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.156.136.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 149.62.192.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 193.193.171.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.193.182.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.194.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.194.155.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a12:4700::/32 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS29244: AS-CETINBG-OUT. 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 (AS29244 isn't in the set, or no route object for AS29244 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 | AS29244 in it | Not covered |
|---|---|---|---|---|---|
| AS-CETINBG-OUT | RIPE | 26 | 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 15 are in fix.csv.
- Route object: none11
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 85.118.192.0/24 | No route object for it. A route object for 85.118.192.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
| Route object: none | 85.118.196.0/24 | No route object for it. A route object for 85.118.192.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
| Route object: none | 87.120.79.0/24 | No route object for it. A route object for 87.120.72.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
| Route object: none | 91.92.8.0/24 | No route object for it. A route object for 91.92.8.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
| Route object: none | 91.92.9.0/24 | No route object for it. A route object for 91.92.8.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
| Route object: none | 91.92.10.0/24 | No route object for it. A route object for 91.92.8.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
| Route object: none | 91.92.11.0/24 | No route object for it. A route object for 91.92.8.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
| Route object: none | 91.92.12.0/24 | No route object for it. A route object for 91.92.8.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
| Route object: none | 91.92.13.0/24 | No route object for it. A route object for 91.92.8.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
| Route object: none | 91.92.14.0/24 | No route object for it. A route object for 91.92.8.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
| Route object: none | 91.92.15.0/24 | No route object for it. A route object for 91.92.8.0/21 with origin AS29244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29244 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29244 whose prefix no peer sees AS29244 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 87.120.72.0/21 | RIPE | No ROA |
| 91.92.8.0/21 | RIPE | No ROA |
| 149.62.248.0/24 | RIPE | Invalid: maxLength |
| 2a12:4700::/29 | RIPE | 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.