AS56353 FIRSTLINE-AS First Line Software s.r.o.
🇨🇿Org handle: ORG-FLSS2-RIPE
-----BEGIN TOKEN-----804ab545259aae5a56a8cc021de2940aef2df55ff43c12372267b3ae91df74e1d6f221290400203fe98d8502d244872071237f2cf9cf9c7f9034d486c02a1cc0-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.225.128.0/22 | 🇨🇿 CZ | RIPENCC | assigned |
All 1 announced prefix of AS56353 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS56353 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS1
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 AS56353 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/56353Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/56353" | jq