AS8896 XFIBER-AS GLOBALCONNECT AS
π³π΄Org handle: ORG-BNA1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
29total
21 IPv48 IPv6
IPv4 Addresses
Allocated (RIR)27,648
Announced (BGP)28,672
IPv6 Addresses
Allocated (RIR)1.3Γ10Β³β°
Announced (BGP)1.7Γ10Β³β°
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
50
Country
π³π΄ NORIR
RIPE NCCStatus
allocated
Allocated
1998-07-23
Announced Prefixes
(BGP)29|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-11 | |
| No ROA | - | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 29
1 / 3
Allocated Prefixes
(RIR)20Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.90.36.0/24 | π³π΄ NO | RIPE | assigned |
| 45.90.37.0/24 | π³π΄ NO | RIPE | assigned |
| 45.138.236.0/22 | π³π΄ NO | RIPENCC | allocated |
| 45.138.238.0/24 | π©π° DK | RIPE | assigned |
| 45.138.239.0/24 | πΈπͺ SE | RIPE | assigned |
| 77.241.96.0/20 | π³π΄ NO | RIPENCC | allocated |
| 81.29.32.0/20 | π³π΄ NO | RIPENCC | allocated |
| 89.221.96.0/20 | π³π΄ NO | RIPENCC | allocated |
| 91.188.232.0/22 | π³π΄ NO | RIPENCC | allocated |
| 185.15.216.0/22 | π³π΄ NO | RIPENCC | allocated |
1-10 of 20
1 / 2
All 29 announced prefixes of AS8896 β
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS8896 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (11)
Networks whose own prefixes AS8896 passes on: usually its customers.
- AS2116GlobalConnect AS2116 GLOBALCONNECT10
- AS201454UPHEADS3
- AS212642RUNNANE Jon Tungland3
- AS4913Speedcast Communications2
- AS50229RIGNET SOIL Rignet AS2
- AS201888CEGAL2
- AS22717Halliburton Company1
- AS48680NETPOWER IT Solutions AS1
- AS202174EMSP FLOW RETAIL AS1
- AS205238Timeit1
- AS213148WintershallDeaNorge Harbour Energy Norge1
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 AS8896 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/8896Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/8896" | jq