Data as of Nov 14, 2026

31.216.24.0/22

No anonymizer space · no proxy exits in 30 days

Bassac SA

Announcement

31.216.16.0/20

RPKI valid

Announced by

AS49463

Type

Business

Risk

0 / 100 · Low

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

Range	Addresses	Netname	Holder	Type	Created	Abuse contact
31.216.16.0/20	4,096	FR-L-N-C-SA-20110509	Bassac SA (ORG-LNCS2-RIPE) · FR	ALLOCATED PA	May 9, 2011	abuse@lncsa.fr
└ 31.216.24.64/26	64	LNCSA-BOULOGNE-Fondation-B4	LNC Boulogne	ASSIGNED PA	Feb 10, 2017	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.128/32	1	NET-LNC-CF-v4_001	CF	ASSIGNED PA	Mar 18, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.129/32	1	NET-LNC-CF-v4_002	CF	ASSIGNED PA	Mar 18, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.130/32	1	NET-LNC-CF-v4_003	CF	ASSIGNED PA	Mar 18, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.131/32	1	NET-LNC-CF-v4_004	CF	ASSIGNED PA	Mar 18, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.132/32	1	NET-LNC-CF-v4_005	CF	ASSIGNED PA	Mar 18, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.133/32	1	NET-LNC-CF-v4_006	CF	ASSIGNED PA	Mar 18, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.134/32	1	NET-LNC-CF-v4_007	CF	ASSIGNED PA	Mar 18, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.135/32	1	NET-LNC-CF-v4_008	CF	ASSIGNED PA	Mar 18, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.136/30	4	NET-LNC-FDISSAUX-v4_001	Freddy DISSAUX	ASSIGNED PA	Oct 26, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.140/30	4	NET-LNC-JGUASCO-v4_001	Jeremy GUASCO	ASSIGNED PA	Oct 26, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.24.192/26	64	LNCSA-BOULOGNE-Fondation-B3	LNC Boulogne	ASSIGNED PA	Feb 10, 2017	abuse@lncsa.fr via FR-L-N-C-SA-20110509
└ 31.216.25.0 - 31.216.27.255	768	LNCSA-BOULOGNE	LNC Boulogne	ASSIGNED PA	Mar 18, 2016	abuse@lncsa.fr via FR-L-N-C-SA-20110509

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Announcement Routing history RPKI & IRR Whois & abuse

Routing timeline

Who has announced 31.216.16.0/20

31.216.16.0/20

Routing history

Pattern: Stable
First seen: Jan 2014
Current origin since: Jan 2014 · 13 yr
Origin networks: 1

RPKI

Route origin authorizations

ROA prefix	ASN	Max len	Anchor	Verdict
31.216.16.0/20	AS49463	/24	RIPE	RPKI valid

IRR

Route objects on 31.216.16.0/20

Origin	Registry	Description	Maintainer	Modified
AS49463	RIPE	LNCSA-BGP-ALL-4-002-16_20	LNCSA-MNT	Jun 28, 2012