Network · data from 2026-11-12
AS198259 ECOM-SERVICE-AS ECOM SERVICE AD
Registry name: ECOM-SERVICE-AS ECOM SERVICE AD, BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198259, 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.
| 145.255.202.0/24 | Valid | Nonecovered by 145.255.202.0/23 | 673 100% |
| 145.255.203.0/24 | Valid | Nonecovered by 145.255.202.0/23 | 673 100% |
| 145.255.204.0/24 | Valid | Nonecovered by 145.255.204.0/23 | 673 100% |
| 145.255.205.0/24 | Valid | Nonecovered by 145.255.204.0/23 | 673 100% |
| 145.255.192.10/32 | Valid | Nonecovered by 145.255.192.0/24 | 4 1%low visibility |
| 145.255.192.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.193.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.194.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.196.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.197.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.198.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.199.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.200.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.201.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.206.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.207.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.208.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.210.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.211.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.212.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.213.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.217.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.218.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.219.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.255.221.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS198259 isn't in PeeringDB, where networks name their AS-SET.
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 12 are in fix.csv.
- Route object: none5
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 145.255.202.0/24 | No route object for it. A route object for 145.255.202.0/23 with origin AS198259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198259 in the RIR database for the space. |
| Route object: none | 145.255.203.0/24 | No route object for it. A route object for 145.255.202.0/23 with origin AS198259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198259 in the RIR database for the space. |
| Route object: none | 145.255.204.0/24 | No route object for it. A route object for 145.255.204.0/23 with origin AS198259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198259 in the RIR database for the space. |
| Route object: none | 145.255.205.0/24 | No route object for it. A route object for 145.255.204.0/23 with origin AS198259 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198259 in the RIR database for the space. |
| Route object: none | 145.255.192.10/32 | No route object for it. A route object for 145.255.192.0/24 with origin AS198259 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS198259 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS198259 whose prefix no peer sees AS198259 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 145.255.192.0/19 | RIPE | No ROA |
| 145.255.192.0/21 | RIPE | No ROA |
| 145.255.202.0/23 | RIPE | No ROA |
| 145.255.204.0/23 | RIPE | No ROA |
| 145.255.208.0/22 | RIPE | No ROA |
| 145.255.212.0/23 | RIPE | No ROA |
| 2a03:8f60::/32 | 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.