Asyncronous Transfer Mode Communication AS

Data as of 2026-10-11
BGP inherited
This organisation
Netblocks6 · 2,048 IPv4 addresses
Record ID247048900
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
194.35.228.0/22 Asyncronous Transfer Mode Communication AS BGP ANNOUNCED ● high
194.35.228.0/23 Asyncronous Transfer Mode Communication AS RIPE ASSIGNED PA ● high
194.35.230.0/23 Asyncronous Transfer Mode Communication AS RIPE ASSIGNED PA ● high
194.99.40.0/22 Asyncronous Transfer Mode Communication AS BGP ANNOUNCED ● high
194.99.40.0/23 Asyncronous Transfer Mode Communication AS RIPE ASSIGNED PA ● high
194.99.42.0/23 Asyncronous Transfer Mode Communication AS RIPE ASSIGNED PA ● high

Footprint over time

10 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-09-06

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
Possible discrepancies (6)

These blocks are registered to Asyncronous Transfer Mode Communication AS but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

194.35.228.0/22 /22 authorized for AS50304 — Blix Solutions AS
194.99.40.0/22 /22 authorized for AS50304 — Blix Solutions AS
194.99.40.0/23 /23 authorized for AS50304 — Blix Solutions AS
194.99.42.0/23 /23 authorized for AS50304 — Blix Solutions AS
194.35.228.0/23 /23 authorized for AS50304 — Blix Solutions AS
194.35.230.0/23 /23 authorized for AS50304 — Blix Solutions AS

NIC Handles

AS213043 BLIX-MNT BLIX-MNT DUMY-RIPE DUMY-RIPE ORG-ATMC2-RIPE