Breadbyte

Registry
Cluster stats
Netblocks9
Registered in Switzerland (2) · United States (2)
Cluster ID211789873
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
149.112.29.109/32 Breadbyte PEERINGDB ASSIGNED ● high
149.112.50.135/32 Breadbyte PEERINGDB ASSIGNED ● high
185.0.30.38/32 Breadbyte PEERINGDB ASSIGNED ● high
185.1.147.17/32 Breadbyte PEERINGDB ASSIGNED ● high
2001:504:125:e0::109/128 Breadbyte PEERINGDB ASSIGNED ● high
2001:504:125:e1::135/128 Breadbyte PEERINGDB ASSIGNED ● high
2001:7f8:ca:1:0:21:3768:1/128 Breadbyte PEERINGDB ASSIGNED ● high
2001:7f8:11c:1:0:21:3768:1/128 Breadbyte PEERINGDB ASSIGNED ● high
2a0c:9a40:8ad0::/48 breadbyte-cloud RIPE ASSIGNED ● low

Network trust

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

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

2a0c:9a40:8ad0::/48 /48 authorized for AS213768 — Thomas Neumann

NIC Handles

AS213768 BREADBYTE-MNT DUMY-RIPE DUMY-RIPE