Your IP: Checking...

Rofnet (AS402164)

Personal homelab ASN used for learning and experimentation (BGP, IP, routing policy, and self-hosted services). Not a commercial network and no SLA.

  • ASN: 402164
  • IPv6: 2620:5a:d000::/48
  • IPv4: 23.144.84.0/24
  • Upstream transits: AS21700 — NYC, AS20473 — NJ
  • PeeringDB: net/41458
  • RPKI (RIPEstat): (v6) (v4)
  • IRR (Route Objects): (v6) (v4)

About

Rofnet (AS402164) is a personal homelab network used to experiment with IP routing, BGP announcements, and basic network operations. Outages and maintenance may occur without notice.

Goals

Learn by doing: BGP policy, filtering, monitoring, and safe operations.

Scope

Multi-homed anycast with upstream transit via Neptune Networks and Vultr. No transit offered to third parties.

Services

Self-hosted services and labs (details intentionally minimal).

Routing notes

Upstream transits

  • Transit 1: Neptune Networks (AS21700) — New York City
  • Transit 2: Vultr (AS20473) — Piscataway, NJ

Announcements

  • IPv6: 2620:5a:d000::/48
  • IPv4: 23.144.84.0/24

Policy (informal)

  • Best-effort only; no guarantees.
  • No transit or downstream customers (origin-only).
  • Receives upstream transit from AS21700 (NYC) and AS20473 (New Jersey).
  • Multi-homed anycast announcements (same prefixes announced from multiple locations/providers).
  • Filtering/security: RPKI (ROAs) + IRR-based hygiene.
  • See PeeringDB for peering/contact details that need to stay current.
Rofnet (AS402164)
  - Upstream transits:
    - AS21700 (Neptune Networks) — New York, NY
    - AS20473 (Vultr) — Piscataway, NJ
  - IPv6: 2620:5a:d000::/48
  - IPv4: 23.144.84.0/24
  - Anycast: yes (multi-homed announcements)
  - RPKI: enabled (ROAs published)
  - IRR: route objects present (ARIN IRR) — see IRR Explorer
  - PeeringDB: https://www.peeringdb.com/net/41458

Registry & routing security

Public references for registration, IRR objects, and RPKI visibility.

RPKI (ROAs)

IRR (route/route6 objects)

Status

Manual status for now. Monitoring/status tooling may be added later.

Current

  • Routing: OK (manual)
  • Connectivity: OK (manual)
  • Maintenance: None announced

Links

Contact

NOC / Ops

Technical

Abuse

For routing issues: include prefix, timestamp (UTC), and observed AS path.