AS204957 GREENFLOID-AS ROUTE 95 LLC
πΊπΈOrg handle: ORG-RL646-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
166total
147 IPv419 IPv6
IPv4 Addresses
Allocated (RIR)36,864
Announced (BGP)43,520
IPv6 Addresses
Allocated (RIR)1.1Γ10Β³β°
Announced (BGP)1.1Γ10Β³β°
Prefix Limit (IPv4)
500
Prefix Limit (IPv6)
100
Country
πΊπΈ USRIR
RIPE NCCStatus
allocated
Allocated
2017-11-30
Announced Prefixes
(BGP)166|
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 | |
| No ROA | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
1-10 of 166
1 / 17
Allocated Prefixes
(RIR)143Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.34.176.0/23 | πΈπ¬ SG | RIPE | assigned |
| 5.183.129.0/24 | π¨π¦ CA | RIPE | assigned |
| 31.222.242.0/24 | πΈπ¨ SC | RIPENCC | allocated |
| 31.222.249.0/24 | πΈπ¨ SC | RIPENCC | allocated |
| 45.84.178.0/24 | π¨π¦ CA | RIPE | assigned |
| 45.90.56.0/22 | πΊπΈ US | RIPENCC | allocated |
| 45.128.149.0/24 | πΊπΈ US | RIPE | assigned |
| 45.137.155.0/24 | πΊπΈ US | RIPE | assigned |
| 46.28.67.0/24 | πΊπΈ US | RIPE | assigned |
| 46.28.70.0/24 | π¨πΏ CZ | RIPE | assigned |
1-10 of 143
1 / 15
All 166 announced prefixes of AS204957 β
BGP Neighbours
(seen in AS paths)Upstreams (11)
Networks AS204957 hands its own prefixes to: transit providers, or peers at an exchange.
Transfer History
Registry transfers of AS204957 between organisations.
- AS204957Transfer Β·
- AS204957Transfer Β·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| AS204957 | GREEN FLOID LLC | ROUTE 95 LLC | Transfer | |
| AS204957 | ITL-Bulgaria Ltd. | GREEN FLOID LLC | Transfer |
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 AS204957 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/204957Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/204957" | jq