Network · data from 2026-11-12
AS18867 AMERICAN-MESSAGING - American Messaging Services L.L.C.
Registry name: AMERICAN-MESSAGING - American Messaging Services L.L.C., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18867, 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.148.155.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 199.245.204.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 204.52.224.0/24 | Invalid: origin | None | 2 0%low visibility |
| 204.75.197.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 204.75.198.0/24 | Invalid: origin | None | 2 0%low visibility |
| 204.75.199.0/24 | Invalid: origin | None | 2 0%low visibility |
| 204.153.80.0/24 | Invalid: origin | None | 2 0%low visibility |
| 63.97.58.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
AS18867 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 16 are in fix.csv.
- ROA: origin7
- ROA: none1
- Route object: none7
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 198.148.155.0/24 | ROAs covering it name AS8075, not AS18867. If AS18867 should announce it, add a ROA for AS18867. |
| Route object: none | 198.148.155.0/24 | Route objects for it name AS8075. Add a route object with origin AS18867 in the RIR database for the space. |
| ROA: origin | 199.245.204.0/24 | ROAs covering it name AS8075, not AS18867. If AS18867 should announce it, add a ROA for AS18867. |
| Route object: none | 199.245.204.0/24 | Route objects for it name AS8075. Add a route object with origin AS18867 in the RIR database for the space. |
| ROA: origin | 204.52.224.0/24 | ROAs covering it name AS8075, not AS18867. If AS18867 should announce it, add a ROA for AS18867. |
| Route object: none | 204.52.224.0/24 | No route object for it. Add a route object with origin AS18867 in the RIR database for the space. |
| ROA: origin | 204.75.197.0/24 | ROAs covering it name AS8075, not AS18867. If AS18867 should announce it, add a ROA for AS18867. |
| Route object: none | 204.75.197.0/24 | Route objects for it name AS8075. Add a route object with origin AS18867 in the RIR database for the space. |
| ROA: origin | 204.75.198.0/24 | ROAs covering it name AS8075, not AS18867. If AS18867 should announce it, add a ROA for AS18867. |
| Route object: none | 204.75.198.0/24 | No route object for it. Add a route object with origin AS18867 in the RIR database for the space. |
| ROA: origin | 204.75.199.0/24 | ROAs covering it name AS8075, not AS18867. If AS18867 should announce it, add a ROA for AS18867. |
| Route object: none | 204.75.199.0/24 | No route object for it. Add a route object with origin AS18867 in the RIR database for the space. |
| ROA: origin | 204.153.80.0/24 | ROAs covering it name AS8075, not AS18867. If AS18867 should announce it, add a ROA for AS18867. |
| Route object: none | 204.153.80.0/24 | No route object for it. Add a route object with origin AS18867 in the RIR database for the space. |
| ROA: none | 63.97.58.0/24 | No ROA covers it. Add a ROA for AS18867, maxLength 24. |
| Route object: RIR | 63.97.58.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS18867 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.