Moefire Network

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks6
IPv6 5 prefixes (largest 2406:840:1f:1000:0:13:7908:1/128)
Record ID246711798
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.155.134/32 Moefire Network PEERINGDB ASSIGNED ● high
2406:840:1f:1000:0:13:7908:1/128 Moefire Network PEERINGDB ASSIGNED ● high
2a0c:b641:701:0:a5:137:908:1/128 Moefire Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:24::1bf/128 Moefire Network PEERINGDB ASSIGNED ● high
2a0e:8f01:1000:32::133/128 Moefire Network PEERINGDB ASSIGNED ● high
2a14:7580:730::5/128 Moefire Network PEERINGDB ASSIGNED ● high

IPv6 ranges (5)

Footprint over time

12 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-10-04

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (3 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS137908