Autonomous system detail

AS708

Not announced

Operated by SB-COMM-AS - Sentinel Byte Community.

Summary

// analyst note
Dormant/legacy ASN with no live routing footprint. All four routing sources (RIPEstat, CAIDA, bgp.he.net, bgp.tools) agree on zero announcements, zero peers, zero cone. Allocation date (1990-06-15) is the autnum object's own top-level RDAP registration event, independently corroborated by bgp.tools; entity-level dates for the registrant org and the POC were excluded as decoys per instructions.
// security note
NEUTRAL/DATED: no notable public abuse signal found as of 2026-07-25; not in Spamhaus ASN-DROP, AbuseIPDB (no ASN page on file), or NANOG mailing-list archives.
IPv4 prefixes
0
~0 addresses
IPv6 prefixes
0
Peer networks
0
0 up · 0 down
IANA block
1-1876
Assigned by ARIN
[ 01 ] — Context

About this ASN.

Updated  ·  Confidence: Medium

AS708 (SB-COMM-AS) is a dormant, legacy autonomous system registered under ARIN to Sentinel Byte Community (org handle SBC-74) that currently announces zero IPv4 and zero IPv6 prefixes and has no live BGP peers, upstreams, or customers — it is registered but effectively absent from the global routing table.

ARIN RDAP records a top-level autnum registration event of 1990-06-15 and a last-changed event of 1991-01-10; bgp.tools independently corroborates the 1990-06-15 registration date. The listed technical/abuse point of contact, Paul S. Kim of The MITRE Corporation (Bedford, MA), has been flagged by ARIN as unresponsive since 2010-06-19, though the registration itself remains in active (not reclaimed) status.

Every routing source consulted agrees on the dormancy: RIPEstat shows 0 of 328 IPv4 and 0 of 324 IPv6 RIS peers seeing the ASN, with empty first-seen/last-seen fields and no historical announcements across its lookback window. CAIDA AS Rank places AS708 at 79,459 with a singleton customer cone (itself, 0 prefixes, 0 addresses) and zero customer/peer/provider degree; bgp.he.net and bgp.tools both confirm zero announced prefixes and no BGP activity.

RPKI posture cannot be assessed because there are no announced prefixes and therefore no ROAs. No PeeringDB record exists for the ASN, and no operator website, notable historical usage, or NANOG/Reddit community references were found — this appears to be an inactive registration with minimal public footprint beyond its ARIN record.

Operator
Sentinel Byte Community (ARIN org handle SBC-74) [Confirmed] — https://rdap.arin.net/registry/autnum/708
Country / RIR
US, ARIN [Confirmed] — https://rdap.arin.net/registry/autnum/708, https://stat.ripe.net/AS708
Allocated
1990-06-15 (ARIN RDAP top-level autnum registration event); last changed 1991-01-10 [Confirmed] — https://rdap.arin.net/registry/autnum/708 (corroborated independently by https://bgp.tools/as/708)
Org status
ARIN registration status active (not reclaimed/revoked), but operationally dormant; technical/abuse POC (The MITRE Corporation contact) flagged unresponsive by ARIN since 2010-06-19 [Confirmed] — https://rdap.arin.net/registry/autnum/708
Contacts
Paul S. Kim, The MITRE Corporation, Bedford, MA — POC unresponsive since 2010-06-19 per ARIN; the on-file address is an individual mailbox on a legacy MITRE host and is not republished here [Confirmed] — https://rdap.arin.net/registry/autnum/708, https://stat.ripe.net/AS708

Security/abuse context (NEUTRAL, DATED)

no notable public abuse signal found as of 2026-07-25 — not in Spamhaus ASN-DROP, AbuseIPDB (no ASN page on file, HTTP 404), or NANOG archives

[Likely] — https://www.spamhaus.org/drop/asndrop/, https://www.abuseipdb.com/asn/708

Network & routing

Network type
legacy/dormant — zero announced prefixes, zero peers, no PeeringDB record; ARIN status remains "active" [Likely] — https://ipinfo.io/AS708, https://rdap.arin.net/registry/autnum/708
Size
dormant — 0 IPv4 prefixes / 0 IPv4 addresses and 0 IPv6 prefixes; customer cone = singleton (1 ASN, 0 prefixes, 0 addresses); CAIDA AS rank 79,459 [Confirmed] — https://stat.ripe.net/AS708, https://asrank.caida.org/asns/708, https://bgp.he.net/AS708, https://bgp.tools/as/708
Routing/peering
NOT announced — 0 of 328 v4 / 0 of 324 v6 RIS peers seeing it; CAIDA degree total 0 (customer 0, peer 0, provider 0); empty RIPEstat first_seen/last_seen (no historical announcement footprint in the covered window); no PeeringDB record found [Confirmed for routing state]. Peering policy Unknown/not published
[Unknown] — https://stat.ripe.net/AS708, https://asrank.caida.org/asns/708
RPKI
not assessable — AS708 announces no prefixes, so there are no ROAs to validate [Confirmed] — https://stat.ripe.net/AS708, https://bgp.tools/as/708
Notable usage
Unknown — no NANOG, Reddit, or news references found specific to AS708 [Unknown] — https://mailman.nanog.org/pipermail/nanog/
Related ASNs
none identified [Unknown]
Analyst note
Registered legacy ASN with no live routing footprint across any source checked (RIPEstat, CAIDA, bgp.he.net, bgp.tools all agree on zero announcements). Allocation date recorded from the ARIN RDAP autnum top-level registration event, not from entity-level dates (registrant org SBC-74 or POC PSK-ARIN carry their own distinct, non-authoritative dates that were excluded).
[ 02 ] — Announced prefixes

What this network routes.

0 prefixes total · RIPEstat data · cached, not real-time
// IPv4 prefixes0
No IPv4 prefixes announced.
// IPv6 prefixes0
No IPv6 prefixes announced.
[ 03 ] — Notable peers & upstreams

Who it talks to.

0 observed neighbours
Neighbour data unavailable from public BGP collectors.