AS48185 team_blue team.blue NV
🇧🇪Org handle: ORG-TN115-RIPE
team.blue backbone
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Routing hygiene
Score 20/100 · Low riskRPKI ROA coverage
50%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
2
diversity 50/100
- 50% of announced prefixes (1 of 2) have no valid ROA
Based on 2 announced prefixes, updated daily (2026-10-20). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-21 | |
| Valid | RIPE | 2026-10-21 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 195.90.96.0/23 | 🇬🇧 GB | RIPENCC | assigned |
| 2a02:2b8::/32 | 🇧🇪 BE | RIPENCC | allocated |
All 2 announced prefixes of AS48185 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS49935 | 🇧🇪SmartEye SmartEye B.V |
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS48185 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS48185 passes on: usually its customers.
Other adjacent networks (7)
Adjacent to AS48185 in the transit part of AS paths: peers, providers or customers.
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/48185Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/48185" | jq