AS201029 RedgeGuardian-AntiDDOS Redge Technologies sp. z o.o.
🇵🇱Org handle: ORG-ASsz2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
8total
2 IPv46 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)7.2×10²⁴
Announced Prefixes
(BGP)8|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| 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 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.77.76.0/24 | 🇪🇺 EU | RIPE | assigned |
All 8 announced prefixes of AS201029 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201029 hands its own prefixes to: transit providers, or peers at an exchange.
- AS57811RedgeTechnologies Redge Technologies Sp. Z O.O8
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 AS201029 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/201029Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201029" | jq