Network · data from 2026-11-12
AS20657 Atlantis BG
Registry name: ATLANTIS ATLANTIS BG Ltd., BG · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20657, 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.95.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 87.246.47.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 87.246.48.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 85.118.94.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 87.246.49.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 88.80.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 88.80.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 88.80.133.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 88.80.152.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 193.108.24.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.79.12.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.79.12.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.79.13.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.68.214.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.68.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.68.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS20657: AS-ATL. 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 (AS20657 isn't in the set, or no route object for AS20657 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 | AS20657 in it | Not covered |
|---|---|---|---|---|---|
| AS-ATL | RIPE | 7 | 1 | Yes | 5 |
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 10 are in fix.csv.
- ROA: origin5
- Route object: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 85.118.95.0/24 | ROAs covering it name AS8717, AS47453, not AS20657. If AS20657 should announce it, add a ROA for AS20657. |
| Route object: none | 85.118.95.0/24 | Route objects for it name AS47453. Add a route object with origin AS20657 in the RIR database for the space. |
| ROA: origin | 87.246.47.0/24 | ROAs covering it name AS47453, not AS20657. If AS20657 should announce it, add a ROA for AS20657. |
| Route object: none | 87.246.47.0/24 | Route objects for it name AS47453. Add a route object with origin AS20657 in the RIR database for the space. |
| ROA: origin | 87.246.48.0/24 | ROAs covering it name AS47453, not AS20657. If AS20657 should announce it, add a ROA for AS20657. |
| Route object: none | 87.246.48.0/24 | Route objects for it name AS47453. Add a route object with origin AS20657 in the RIR database for the space. |
| ROA: origin | 85.118.94.0/24 | ROAs covering it name AS8717, AS47453, not AS20657. If AS20657 should announce it, add a ROA for AS20657. |
| Route object: none | 85.118.94.0/24 | Route objects for it name AS47453. Add a route object with origin AS20657 in the RIR database for the space. |
| ROA: origin | 87.246.49.0/24 | ROAs covering it name AS47453, not AS20657. If AS20657 should announce it, add a ROA for AS20657. |
| Route object: none | 87.246.49.0/24 | Route objects for it name AS47453. Add a route object with origin AS20657 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS20657 is announced.
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.