Autonomous system
AS13846 LAVALIFE - Lavalife Corp.
Unclassified ARIN
Summary
Lavalife
media business enterprise
Three contiguous blocks, one netname, one upstream, and a brand that outlived the company that built it.
What it's used for
- An online dating service's network. 1,280 addresses across three IPv4 prefixes, one observed BGP neighbour, and no IPv6 announced.
Notable
- All three prefixes begin
208.68.20, pieces of one parent range announced separately. - The two
/23s are not adjacent:208.68.202.0and208.68.204.0leave a gap between them. - All three are netname
LAVALIFE-CORP, registered to the same company. - One upstream carries everything.
- Nine addresses were queried for reverse DNS and none returned a name.
Interesting
- Announcing three pieces of one range separately, to a single upstream, achieves nothing the parent announcement would not. The gap between the two larger pieces says the missing block went somewhere else, and whoever held it announced it from their own AS.
- A consumer service with nothing answering a reverse lookup anywhere in its space has moved the public-facing side onto hosting somebody else runs. What is left in the AS is the corporate remainder, which is what happens to brands after the company behind them is bought.
- One neighbour makes the routing a formality: the space is held, not defended.
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.
Transit providers
1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS7311 | Frontier Networks Inc | 264 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-03, 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.28K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| CA | Canada | 3 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS13846- Registry name
- LAVALIFE
- Registrant
- Lavalife Corp.
- Abuse contact
- rob.tolman@lavalife.com
- Registered
- 2006-07-11
- Last changed
- 2012-02-24
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 4 with no ROA
- ROAs
- 0 authorising AS13846
- ASPA
- no ASPA record
- IRR
- 75% registered · 3 of 4 announcements
- Route objects
- 5 naming AS13846
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: 451 networks and 1,853 prefixes, as published 2026-11-04. 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