Network · data from 2026-11-12
AS206105 FLOLIVE-AS floLIVE Bulgaria Ltd.
Registry name: FLOLIVE-AS floLIVE Bulgaria Ltd., BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206105, 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.
| 154.18.14.0/23 | No ROA | None | 673 100% |
| 154.43.170.0/23 | No ROA | None | 673 100% |
| 154.43.173.0/24 | No ROA | None | 673 100% |
| 154.43.180.0/24 | No ROA | None | 673 100% |
| 154.43.181.0/24 | No ROA | None | 673 100% |
| 154.43.184.0/23 | No ROA | None | 673 100% |
| 154.43.164.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 78.41.43.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 152.114.211.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 212.20.134.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 212.20.148.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 2001:67c:c44::/48 | No ROA | RIR databaseRIPE | 633 100% |
| 80.95.21.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS206105 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 20 are in fix.csv.
- ROA: none12
- Route object: none6
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.18.14.0/23 | No ROA covers it. Add a ROA for AS206105, maxLength 23. |
| Route object: none | 154.18.14.0/23 | No route object for it. Add a route object with origin AS206105 in the RIR database for the space. |
| ROA: none | 154.43.170.0/23 | No ROA covers it. Add a ROA for AS206105, maxLength 23. |
| Route object: none | 154.43.170.0/23 | No route object for it. Add a route object with origin AS206105 in the RIR database for the space. |
| ROA: none | 154.43.173.0/24 | No ROA covers it. Add a ROA for AS206105, maxLength 24. |
| Route object: none | 154.43.173.0/24 | No route object for it. Add a route object with origin AS206105 in the RIR database for the space. |
| ROA: none | 154.43.180.0/24 | No ROA covers it. Add a ROA for AS206105, maxLength 24. |
| Route object: none | 154.43.180.0/24 | No route object for it. Add a route object with origin AS206105 in the RIR database for the space. |
| ROA: none | 154.43.181.0/24 | No ROA covers it. Add a ROA for AS206105, maxLength 24. |
| Route object: none | 154.43.181.0/24 | No route object for it. Add a route object with origin AS206105 in the RIR database for the space. |
| ROA: none | 154.43.184.0/23 | No ROA covers it. Add a ROA for AS206105, maxLength 23. |
| Route object: none | 154.43.184.0/23 | No route object for it. Add a route object with origin AS206105 in the RIR database for the space. |
| ROA: none | 154.43.164.0/24 | No ROA covers it. Add a ROA for AS206105, maxLength 24. |
| Route object: RIR | 154.43.164.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 78.41.43.0/24 | No ROA covers it. Add a ROA for AS206105, maxLength 24. |
| ROA: none | 152.114.211.0/24 | No ROA covers it. Add a ROA for AS206105, maxLength 24. |
| ROA: none | 212.20.134.0/23 | No ROA covers it. Add a ROA for AS206105, maxLength 23. |
| ROA: none | 212.20.148.0/23 | No ROA covers it. Add a ROA for AS206105, maxLength 23. |
| ROA: none | 2001:67c:c44::/48 | No ROA covers it. Add a ROA for AS206105, maxLength 48. |
Route objects not announced
Route objects with origin AS206105 whose prefix no peer sees AS206105 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 154.43.175.0/24 | 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.