INTERSERVE PLC
INTERSERVE
Data as of 2026-08-30
GLEIF verified
LEI
549300MVYY4EZCRFHZ09
Registered name
INTERSERVE PLC
Jurisdiction
Ultimate parent
No parent on file in GLEIF
This organisation
| Netblocks | 4 |
| IPv6 | 3 prefixes (largest 2a00:2381:f27b::/48) |
| Also registered under this name | 5 netblocks across 2 separate records |
| Record ID | 235016270 |
| Registry | RIPE |
| Owner jurisdiction | GB |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | GLEIF legal-entity match |
| Legal identity | LEI 549300MVYY4EZCRFHZ09 |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 217.36.27.40/29 | Interserve | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:f27b::/48 | INTERSERVE | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a00:2381:f29d::/48 | INTERSERVE | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a01:4f8:160:3465::/64 | INTERSERVE-COMMUNICATIONS | RIPE | ASSIGNED | ● low |
IPv6 ranges (3)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (2)
These blocks are registered to INTERSERVE but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a00:2381:f27b::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
| 2a00:2381:f29d::/48 /48 | authorized for AS2856 — British Telecommunications Limited |
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
HOS-GUN