BAGE-SG
Data as of 2026-08-16
BGP inherited
Cluster stats
| Netblocks | 2 · 256 IPv4 addresses |
| IPv6 | 1 prefix (largest 2a0c:9a40:d040::/42) |
| All fragments | 24 blocks across 3 clusters |
| Cluster ID | 222430956 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 10 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 213.218.228.0/24 | BAGE-SG | RIPE | SUB-ALLOCATED PA | ● low |
| 2a0c:9a40:d040::/42 | BAGE-SG | RIPE | ASSIGNED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a0c:9a40:d040::/42 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to BAGE-SG 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.
| 213.218.228.0/24 /24 | authorized for AS395374 — Cyber Sainik |
NIC Handles
AR834
BAGE-MNT
DUMY-RIPE
DUMY-RIPE
ORG-IL687-RIPE
ORG-PC518-RIPE
ORG-PC570-RIPE
PC19291-RIPE
PC19462-RIPE
netutils-mnt