BICS
Cluster stats
Netblocks86
All fragments 132 blocks across 26 clusters
Cluster ID193372683
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (86)

showing 50 of 86 — see all — ⬇ export CSV
CIDR Org name Registry Status Confidence
5.57.80.170/32 BICS PEERINGDB ASSIGNED ● high
27.111.229.66/32 BICS PEERINGDB ASSIGNED ● high
37.49.232.93/32 BICS PEERINGDB ASSIGNED ● high
37.49.236.57/32 BICS PEERINGDB ASSIGNED ● high
80.81.192.12/32 BICS PEERINGDB ASSIGNED ● high
80.249.208.87/32 BICS PEERINGDB ASSIGNED ● high
80.249.209.76/32 BICS PEERINGDB ASSIGNED ● high
103.16.102.52/32 BICS PEERINGDB ASSIGNED ● high
103.162.254.67/32 BICS PEERINGDB ASSIGNED ● high
103.247.139.56/32 BICS PEERINGDB ASSIGNED ● high
123.255.91.90/32 BICS PEERINGDB ASSIGNED ● high
178.18.236.23/32 BICS PEERINGDB ASSIGNED ● high
178.18.236.229/32 BICS PEERINGDB ASSIGNED ● high
185.1.8.56/32 BICS PEERINGDB ASSIGNED ● high
185.1.47.29/32 BICS PEERINGDB ASSIGNED ● high
185.1.94.34/32 BICS PEERINGDB ASSIGNED ● high
185.1.222.170/32 BICS PEERINGDB ASSIGNED ● high
188.93.170.103/32 BICS PEERINGDB ASSIGNED ● high
193.189.82.23/32 BICS PEERINGDB ASSIGNED ● high
193.203.0.174/32 BICS PEERINGDB ASSIGNED ● high
193.239.117.210/32 BICS PEERINGDB ASSIGNED ● high
193.239.117.211/32 BICS PEERINGDB ASSIGNED ● high
193.239.117.212/32 BICS PEERINGDB ASSIGNED ● high
194.53.172.68/32 BICS PEERINGDB ASSIGNED ● high
194.68.129.173/32 BICS PEERINGDB ASSIGNED ● high
195.42.144.108/32 BICS PEERINGDB ASSIGNED ● high
195.66.224.128/32 BICS PEERINGDB ASSIGNED ● high
195.66.225.97/32 BICS PEERINGDB ASSIGNED ● high
196.60.8.87/32 BICS PEERINGDB ASSIGNED ● high
196.60.10.159/32 BICS PEERINGDB ASSIGNED ● high
196.60.58.16/32 BICS PEERINGDB ASSIGNED ● high
196.60.71.135/32 BICS PEERINGDB ASSIGNED ● high
196.60.114.5/32 BICS PEERINGDB ASSIGNED ● high
196.60.124.22/32 BICS PEERINGDB ASSIGNED ● high
196.216.148.74/32 BICS PEERINGDB ASSIGNED ● high
196.223.21.77/32 BICS PEERINGDB ASSIGNED ● high
196.223.38.212/32 BICS PEERINGDB ASSIGNED ● high
198.32.160.202/32 BICS PEERINGDB ASSIGNED ● high
198.32.242.183/32 BICS PEERINGDB ASSIGNED ● high
206.81.80.161/32 BICS PEERINGDB ASSIGNED ● high
206.82.104.84/32 BICS PEERINGDB ASSIGNED ● high
206.126.236.228/32 BICS PEERINGDB ASSIGNED ● high
210.173.177.25/32 BICS PEERINGDB ASSIGNED ● high
2001:504:0:2::6774:1/128 BICS PEERINGDB ASSIGNED ● high
2001:504:0:6::6774:1/128 BICS PEERINGDB ASSIGNED ● high
2001:504:1::a500:6774:1/128 BICS PEERINGDB ASSIGNED ● high
2001:504:16::1a76/128 BICS PEERINGDB ASSIGNED ● high
2001:504:36::1a76:0:1/128 BICS PEERINGDB ASSIGNED ● high
2001:7f8::1a76:0:1/128 BICS PEERINGDB ASSIGNED ● high
2001:7f8:1::a500:6774:1/128 BICS PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: C how networks compare →
76.7% of checked blocks have valid RPKI ROA coverage (66 of 86)
Possible discrepancies (1)

These blocks are registered to BICS 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.

2001:9b8:2000::/36 /36 authorized for AS6774 — Belgacom International Carrier Services SA

NIC Handles

AS6774 ATOM86-MNT DUMY-RIPE DUMY-RIPE MNT-BICS