AS63800 SERVER-G SERVER-G Group
Announced Prefixes (BGP)
11total
1 IPv410 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)1.2×10²⁵
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
50
Allocated
-
Announced Prefixes
(BGP)11|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 |
1-10 of 11
1 / 2
All 11 announced prefixes of AS63800 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS63800 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS63800 passes on: usually its customers.
ASPA
No ASPA
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 AS63800 should publish an ASPA object
- IPv4 transfer marketTransfers published by all five RIRs
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/63800Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/63800" | jq