SIN-LAN
BGP inherited
Cluster stats
| Netblocks | 18 |
| Registered in | Germany (6) · Russia (1) |
| Cluster ID | 204930762 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
4 weekly snapshots · JSON
18
0 netblocks since 2026-07-05
2026-07-05
peak 18
2026-07-13
IP Ranges (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 79.134.221.188/30 | SIN-LAN | RIPE | ASSIGNED PA | ● low |
| 87.121.228.64/29 | SIN-LAN | RIPE | ASSIGNED PA | ● low |
| 93.159.106.14/32 | SIN-LAN | RIPE | ASSIGNED PA | ● low |
| 212.99.208.40/29 | SIN-LAN | RIPE | ASSIGNED PA | ● low |
| 212.99.208.48/29 | SIN-LAN | RIPE | ASSIGNED PA | ● low |
| 212.99.208.56/29 | SIN-LAN | RIPE | ASSIGNED PA | ● low |
| 212.99.211.16/29 | SIN-LAN | RIPE | ASSIGNED PA | ● low |
| 2a00:1ca0:900:1f6::/64 | SIN-LAN | RIPE | ASSIGNED | ● low |
| 2a00:1ca0:900:b0a4::/64 | SIN-LAN | RIPE | ASSIGNED | ● low |
| 2a00:1ca0:900:b0a5::/64 | SIN-LAN | RIPE | ASSIGNED | ● low |
| 2a00:1ca0:900:b0a6::/64 | SIN-LAN | RIPE | ASSIGNED | ● low |
| 2a00:1ca0:900:b0a9::/64 | SIN-LAN | RIPE | ASSIGNED | ● low |
| 2a00:1ca0:901:400::/56 | SIN-LAN | RIPE | ASSIGNED | ● low |
| 2a00:1ca0:901:2b00::/56 | SIN-LAN | RIPE | ASSIGNED | ● low |
| 2a00:1ca0:901:2c00::/56 | SIN-LAN | RIPE | ASSIGNED | ● low |
| 2a00:1ca0:901:2d00::/56 | SIN-LAN | RIPE | ASSIGNED | ● low |
| 2a00:1ca0:901:3000::/56 | SIN-LAN | RIPE | ASSIGNED | ● low |
| 2a00:1ca0:a03:1f00::/56 | SIN-LAN | RIPE | ASSIGNED | ● low |
Possibly related to this organisation
what's this?Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- SLED-IZOLYATOR-FSIN-LAN via PJSC MegaFon sub-allocation
- KP5-UFSIN-LAN via PJSC MegaFon sub-allocation
- 7 Ufsin via PJSC MegaFon sub-allocation
- Sysin via PJSC MegaFon sub-allocation
- SML-YARTSEVO-OSIN-LAN via PJSC MegaFon sub-allocation
- Poissin Lan 19527 via Spitfire Network Services Limited sub-allocation
- Poussin Lan 19772 via Spitfire Network Services Limited sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(18 of 18)
Possible discrepancies (6)
These blocks are registered to SIN-LAN 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:1ca0:901:400::/56 /56 | authorized for AS21413 — Envia Tel GmbH |
| 2a00:1ca0:a03:1f00::/56 /56 | authorized for AS21413 — Envia Tel GmbH |
| 2a00:1ca0:901:2b00::/56 /56 | authorized for AS21413 — Envia Tel GmbH |
| 2a00:1ca0:901:2c00::/56 /56 | authorized for AS21413 — Envia Tel GmbH |
| 2a00:1ca0:901:2d00::/56 /56 | authorized for AS21413 — Envia Tel GmbH |
| 2a00:1ca0:901:3000::/56 /56 | authorized for AS21413 — Envia Tel GmbH |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ENVIA-TEL-MNT
OBIT-MNT