Network · data from 2026-11-12
AS49699 ICN-BG SuperHosting.BG Ltd.
Registry name: ICN-BG SuperHosting.BG Ltd., BG · not in PeeringDB
30IPv4 routes
56.7% RPKI valid · 56.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
13No ROA
13 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS49699, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS49699, 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.
| 91.215.219.0/24 | No ROA | Nonecovered by 91.215.216.0/22 | 673 100% |
| 91.230.192.0/24 | No ROA | Nonecovered by 91.230.192.0/22 | 673 100% |
| 91.230.193.0/24 | No ROA | Nonecovered by 91.230.192.0/22 | 673 100% |
| 91.230.194.0/24 | No ROA | Nonecovered by 91.230.192.0/22 | 673 100% |
| 91.230.195.0/24 | No ROA | Nonecovered by 91.230.192.0/22 | 673 100% |
| 195.69.164.0/24 | No ROA | Nonecovered by 195.69.164.0/22 | 673 100% |
| 195.69.165.0/24 | No ROA | Nonecovered by 195.69.164.0/22 | 673 100% |
| 195.69.166.0/24 | No ROA | Nonecovered by 195.69.164.0/22 | 673 100% |
| 195.69.167.0/24 | No ROA | Nonecovered by 195.69.164.0/22 | 673 100% |
| 91.215.216.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.215.217.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.215.218.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.41.64.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 77.77.148.0/24 | Valid | Nonecovered by 77.77.148.0/22 | 672 100% |
| 77.77.149.0/24 | Valid | Nonecovered by 77.77.148.0/22 | 672 100% |
| 77.77.150.0/24 | Valid | Nonecovered by 77.77.148.0/22 | 672 100% |
| 77.77.151.0/24 | Valid | Nonecovered by 77.77.148.0/22 | 672 100% |
| 5.104.170.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.104.171.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.104.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.104.173.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.142.50.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.124.30.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.118.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.118.241.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.246.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.246.24.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 130.185.253.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.68.112.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.68.113.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS49699 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 30 are in fix.csv.
- ROA: none13
- Route object: none13
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.215.219.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| Route object: none | 91.215.219.0/24 | No route object for it. A route object for 91.215.216.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| ROA: none | 91.230.192.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| Route object: none | 91.230.192.0/24 | No route object for it. A route object for 91.230.192.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| ROA: none | 91.230.193.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| Route object: none | 91.230.193.0/24 | No route object for it. A route object for 91.230.192.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| ROA: none | 91.230.194.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| Route object: none | 91.230.194.0/24 | No route object for it. A route object for 91.230.192.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| ROA: none | 91.230.195.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| Route object: none | 91.230.195.0/24 | No route object for it. A route object for 91.230.192.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| ROA: none | 195.69.164.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| Route object: none | 195.69.164.0/24 | No route object for it. A route object for 195.69.164.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| ROA: none | 195.69.165.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| Route object: none | 195.69.165.0/24 | No route object for it. A route object for 195.69.164.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| ROA: none | 195.69.166.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| Route object: none | 195.69.166.0/24 | No route object for it. A route object for 195.69.164.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| ROA: none | 195.69.167.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| Route object: none | 195.69.167.0/24 | No route object for it. A route object for 195.69.164.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| ROA: none | 91.215.216.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| ROA: none | 91.215.217.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| ROA: none | 91.215.218.0/24 | No ROA covers it. Add a ROA for AS49699, maxLength 24. |
| ROA: none | 193.41.64.0/22 | No ROA covers it. Add a ROA for AS49699, maxLength 22. |
| Route object: none | 77.77.148.0/24 | No route object for it. A route object for 77.77.148.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| Route object: none | 77.77.149.0/24 | No route object for it. A route object for 77.77.148.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| Route object: none | 77.77.150.0/24 | No route object for it. A route object for 77.77.148.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
| Route object: none | 77.77.151.0/24 | No route object for it. A route object for 77.77.148.0/22 with origin AS49699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49699 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49699 whose prefix no peer sees AS49699 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.77.148.0/22 | RIPE | Valid |
| 91.215.216.0/22 | RIPE | No ROA |
| 91.230.192.0/22 | RIPE | No ROA |
| 195.69.164.0/22 | 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.