Network · data from 2026-11-12
AS11230 MHSFL - Managed Hosting Services, LLC
Registry name: MHSFL - Managed Hosting Services, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS11230, 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.
| 198.183.221.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 198.183.220.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 198.183.223.0/24 | Valid | Other IRR onlyRADB | 670 100% |
AS-SET
AS11230 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 5 are in fix.csv.
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 198.183.221.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.183.220.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.183.223.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS11230 whose prefix no peer sees AS11230 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 198.183.220.0/22 | RADB | Valid |
| 198.183.222.0/24 | RADB | Valid |
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.