AS41536 AS-01NODE 01NODE FUNDING SRL
🇷🇴Org handle: ORG-FS376-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)832
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.120.245.128/26 | 🇷🇴 RO | RIPE | assigned |
| 91.198.59.0/24 | 🇷🇴 RO | RIPENCC | assigned |
| 193.222.57.0/24 | 🇷🇴 RO | RIPENCC | assigned |
| 195.14.6.0/24 | 🇷🇴 RO | RIPENCC | assigned |
All 3 announced prefixes of AS41536 →
BGP Neighbours
(seen in AS paths)Transfer History
Registry transfers of AS41536 between organisations.
- AS41536M&A ·
- AS41536Transfer ·
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 AS41536 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/41536Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/41536" | jq