Autonomous system
AS15315 IVANET-CAMBRIDGE-1
Unclassified ARIN
Summary
iBasis
telecom transit business
Two registries name two different cities for the same network.
What it's used for
- An international voice carrier's network. Three IPv4 prefixes announced from the United States, no IPv6, and three observed BGP neighbours.
Notable
- One registry records the handle as
IVANET-LISBONand the other asIVANET-CAMBRIDGE-1, so the same number is filed under two cities on two continents. - Two netnames share a stem with a three letter code that reads as a third city, one with a counter and one without.
- The third netname is the company name in mixed case with a two letter suffix, the only label here that is not built from the shared stem.
- Every block is registered to a network engineering department rather than to the company itself.
- Nine addresses were queried for reverse DNS and none returned a name.
Interesting
- Two cities in two registries is what happens when a network is operated in one place and administered in another, and neither record is wrong. It is a problem only for anyone trying to geolocate the network from its paperwork.
- The blocks sit in a range normally administered by a different regional registry from the one the announcements come from, which is ordinary for a carrier whose business is carrying calls between continents.
- A department as registrant rather than the company is good operational practice and poor identification: it reaches the right engineers and tells an outsider nothing about who owns the space.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-22, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 3 prefixes · 1.02K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 3 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS15315- Registry name
- IBASIS-LISBON
- Registrant
- IBASIS INC.
- Abuse contact
- NetworkEngineering@ibasis.net
- Registered
- 2000-04-17
- Last changed
- 2026-05-12
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 4 with no ROA
- ROAs
- 0 authorising AS15315
- ASPA
- no ASPA record
- IRR
- 0% registered · 0 of 4 announcements
- Route objects
- 2 naming AS15315
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,779 prefixes, as published 2026-10-23. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere