AS6718 NAV NAV COMMUNICATIONS SRL
🇷🇴Org handle: ORG-NCS28-RIPE
NAV Communications
RIPE NCCallocated
Announced Prefixes (BGP)
61total
44 IPv417 IPv6
IPv4 Addresses
Allocated (RIR)11,008
Announced (BGP)11,520
IPv6 Addresses
Allocated (RIR)1.3×10³⁰
Announced (BGP)1.3×10³⁰
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
100
Country
🇷🇴 RORIR
RIPE NCCStatus
allocated
Allocated
2009-07-24
Routing hygiene
Score 13/100 · Low riskRPKI ROA coverage
91.8%
4 prefixes RPKI invalid
IRR route objects
93.4%
3 prefixes registered for another origin
Hijack signals
1
0 announced against others' ROAs, 1 own announced by others
Upstreams
4
diversity 58/100
- 8% of announced prefixes (5 of 61) have no valid ROA, 4 of them RPKI invalid
Based on 61 announced prefixes, updated daily (2026-10-23). How the score works · RPKI explained
Announced Prefixes
(BGP)61|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
| Valid | RIPE | - | |
89.37.186.0/24MOAS | Invalid | - | - |
1-10 of 61
1 / 7
Allocated Prefixes
(RIR)59Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.154.224.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 37.156.37.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 80.96.42.0/24 | 🇷🇴 RO | RIPE | assigned |
| 80.97.49.0/24 | 🇷🇴 RO | RIPE | assigned |
| 81.180.207.0/24 | 🇷🇴 RO | RIPE | assigned |
| 89.35.4.0/24 | 🇷🇴 RO | RIPE | assigned |
| 89.35.5.0/24 | 🇷🇴 RO | RIPE | assigned |
| 89.37.186.0/24 | 🇷🇴 RO | RIPE | assigned |
| 89.37.187.0/24 | 🇷🇴 RO | RIPE | assigned |
| 89.40.133.0/24 | 🇷🇴 RO | RIPENCC | allocated |
1-10 of 59
1 / 6
All 61 announced prefixes of AS6718 →
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS6718 hands its own prefixes to: transit providers, or peers at an exchange.
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS6718 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/6718Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/6718" | jq