AS218568 SGP22-AS Shabalov Grigoriy Pavlovich
🇷🇺Org handle: ORG-SGP22-RIPE
-----BEGIN TOKEN-----e59f2304babf8eb5198ecf8e8d03cc77dece5a8caa0899581d337e3b8f9a107876e28c9eac7d199db9c9f649c8606b5d3cc247d02cdb0f0a783a59d52b3adce9-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
147.45.47.0/24MOAS | Valid | RIPE | 2026-10-10 |
193.5.250.0/24MOAS | Valid | RIPE | 2026-10-10 |
| Valid | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.88.173.0/24 | 🇹🇷 TR | RIPE | assigned |
| 193.160.140.0/24 | 🇹🇷 TR | RIPE | assigned |
| 2a14:a087:14::/48 | 🇷🇺 RU | RIPE | assigned |
All 3 announced prefixes of AS218568 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS218568 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS3
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 AS218568 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/218568Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/218568" | jq