AS197442 NetworkLayer-MB NetworkLayer MB
🇱🇹Org handle: ORG-NLMB1-RIPE
-----BEGIN TOKEN-----0c0a02f18c9395cdd623a498dd19b549c82fb77c39cc22c99409d074f603affd7150e6156271875cf744bb3bb8288b210d4397012688cf2a54f021dfd7e893f9-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)3.1×10²⁶
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Invalid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.84.89.0/24 | 🇬🇧 GB | RIPENCC | allocated |
| 206.109.198.0/24 | 🇬🇧 GB | RIPENCC | allocated |
| 2a06:9801:2fe::/48 | 🇱🇹 LT | RIPE | assigned |
| 2a07:54c1:8a00::/40 | 🇱🇹 LT | RIPE | assigned |
All 2 announced prefixes of AS197442 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS197442 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS2
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS197442 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/197442Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/197442" | jq