AS807

AS807 is an actively announced autonomous system registered to Fork Systems, LLC, a small regional network operator based in Capitol Heights, Maryland, that currently originates three IPv4 prefixes and one IPv6 prefix with near-universal RIS visibility. It is a live, working ASN, not a dormant or legacy registration.

ARIN RDAP shows the autnum's top-level registration event dated 2022-06-15, last changed 2022-06-22, status "active," registrant Fork Systems (handle RT-405) at Capitol Heights, MD, with registrant contact Rina Tajvar. PeeringDB corroborates the operator identity and self-classifies the network as a regional NSP carrying 1-5 Gbps of balanced traffic.

Routing data is well corroborated: RIPEstat shows 328/328 RIS peers seeing the IPv4 announcements and 321/322 seeing the IPv6 announcement, covering 23.147.64.0/24, 193.57.200.0/24, 193.57.223.0/24, and 2620:39:6000::/48 (768 IPv4 addresses plus one /48). CAIDA ranks it 2,642 globally, with a customer cone of 10 ASNs / 113 prefixes / 98,304 addresses and a total degree of 5 (3 customers, 2 providers, 0 settlement peers observed); it is a CAIDA clique member. The individual upstream and peer ASNs are not named in the aggregate CAIDA/RIPEstat payloads, so that detail is Unknown rather than fabricated.

The operator's own website (forksystems.net) is a minimal single-page splash with only a name and logo; /about, /peering, and /network all return HTTP 404, so there is no operator-authored description of usage or customers to draw on. PeeringDB lists an "Open" peering policy with no contract or location requirements, yet reports zero public IX sessions (netixlan) and zero facility presence (netfac) and no looking-glass URL — so despite the stated policy, no public peering footprint is actually documented anywhere found.

Operator

Fork Systems, LLC (ARIN registrant "FORK SYSTEMS," handle RT-405; PeeringDB org/net name "Fork Systems"), Capitol Heights, MD [Confirmed] — ARIN RDAP autnum/807, peeringdb.com/asn/807

Country / RIR

US, ARIN [Confirmed] — RIPEstat abuse-contact-finder, ARIN RDAP

Allocated

2022-06-15 (ARIN RDAP autnum top-level registration event, first-party RIR fact); last changed 2022-06-22 [Confirmed] — rdap.arin.net/registry/autnum/807

Org status

active — ARIN RDAP status "active," PeeringDB org status "ok"; registrant contact Rina Tajvar (ARIN handle TAJVA2-ARIN, holding the technical/administrative/abuse roles) [Confirmed] — rdap.arin.net/registry/autnum/807, peeringdb.com/asn/807

Contacts

the sole point of contact is ARIN handle TAJVA2-ARIN (Rina Tajvar), carrying the technical, administrative and abuse roles; its mailbox and telephone are withheld here because the RDAP vCard declares kind: "individual". There is no role/function mailbox on this record. Registrant organisation FORK SYSTEMS, Capitol Heights, MD

[Confirmed] — rdap.arin.net/registry/autnum/807

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-08-01 via DuckDuckGo, bgp.he.net, ARIN RDAP; Spamhaus and Talos queries returned HTTP 403 and were not directly verified

Network & routing

Network type

regional NSP (Network Service Provider) per PeeringDB self-report; self-reported traffic level 1-5 Gbps, "Balanced" ratio [Confirmed as self-reported PeeringDB field] — peeringdb.com/asn/807

Size

3 IPv4 prefixes / 768 IPv4 addresses announced (23.147.64.0/24, 193.57.200.0/24, 193.57.223.0/24); 1 IPv6 prefix announced (2620:39:6000::/48) [Confirmed] — stat.ripe.net/807 (2026-08-01)

Routing/peering

v4 328/328 RIS peers seeing, v6 321/322 [Confirmed]. CAIDA total degree 5 = 3 customers + 2 providers + 0 peers, clique member [Confirmed]. Upstream/peer ASNs not named in source data [Unknown]. PeeringDB policy "Open," no contract/location requirement, but 0 netixlan / 0 netfac / no looking-glass — no documented public peering footprint [Confirmed]

RPKI

validation status Unknown — the RIPEstat rpki-validation endpoint requires a per-prefix argument and returns nothing for an ASN-level query

Notable usage

no operator-published use case or customer description exists (site has no subpages). bgp.he.net (third-party) shows roughly 4 origin prefixes / ~53 total announced and BGP sessions with GSL Networks, Atlantic Metro Communications II, and Free Range Cloud Hosting — a live snapshot, not an operator statement [Unknown for operator-official usage; Likely for the third-party BGP snapshot] — bgp.he.net/AS807

Related ASNs

none confirmed; bgp.he.net lists BGP session partners (not corporate affiliates) GSL Networks, Atlantic Metro Communications II, Free Range Cloud Hosting [Unknown for org affiliation; Likely for BGP session facts] — bgp.he.net/AS807

Analyst note

upstream/peer ASN names, RPKI validation status, and broader community/reputation corroboration (NANOG, Reddit, outage reports) are not established by any source consulted and are recorded as sourced Unknown rather than fabricated. The RIPEstat rpki-validation endpoint requires a per-prefix argument, so an ASN-level query returns nothing; the CAIDA and RIPEstat aggregate payloads used here do not name individual upstream/peer ASNs.