asn.dev

Autonomous system

AS14574 RTCCOM - RTC Communications

Unclassified ARIN

IPv4 addresses 12.29K 2 prefixes
IPv6 prefixes 1 counted as prefixes, not addresses
Countries 1 mostly US
Exchanges 0 recorded by PCH
Upstreams 2 0 downstream
Flagged prefixes 0 none

Summary

RTC Communications

United States · AI-generated

isp telecom business

One reverse name carries a four-letter code after the address; its neighbour in the sample does not.

What it's used for

  • A rural telephone company's internet network. 12,288 addresses across two IPv4 prefixes plus one IPv6 prefix, 2607:a700::/32, with two observed BGP neighbours.

Notable

  • 216.176.96.0/19 carries the netname RTCC-NB-1 and 168.75.192.0/20 carries RTCC, both registered to RTC Communications, with an Internet Systems Manager contact on the first.
  • Two of six sampled addresses returned a name: 216-176-119-254-WAGF.rtccom.net and 168-75-203-254.rtccom.net.

Interesting

  • The four letters appended to one hostname are a site code, and their absence on the other says the two blocks were built at different times under different conventions. Nobody goes back to rename the older zone once the addresses are working.
  • Holding two blocks from unrelated ranges, one of them from the low 168 space, points at allocations made years apart. A telephone company that has been selling internet access since dial-up accumulates address space the way it accumulates copper.
  • A full /32 of IPv6 alongside 12,288 IPv4 addresses is the standard allocation regardless of size, so a small operator ends up with more IPv6 than it could use in several lifetimes.
  • Two neighbours is the minimum that counts as multihomed, and it is the usual answer for a rural carrier: one primary upstream, one that exists so the first one can fail.

This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.

Interconnection

Peering at a glance

Full topology · Graph

Internet exchanges

No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.

Transit providers

2 upstream, 0 downstream and 3 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS6461Zayo Bandwidth128
AS11550Smithville Digital, LLC18

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-07, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 2 prefixes · 12.29K addresses IPv6 1 prefixes

CountryNamePrefixes
USUnited States of America3

Registry

Allocation record

ARIN · via Atlas (registry + RDAP)
Registry
ARIN
Handle
AS14574
Registry name
RTCCOM
Registrant
RTC Communications
Abuse contact
sdonley@rtccom.com
Registered
2000-01-06
Last changed
2026-09-23
Allocation
assigned

Routing security

RPKI and IRR

Full detail
RPKI
100% valid · 3 valid, 0 with no ROA
ROAs
4 authorising AS14574
ASPA
no ASPA record
IRR
33% registered · 1 of 3 announcements
Route objects
2 naming AS14574

Reputation

Classification and threat

Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.

Spamhaus DROP

Not on ASN-DROP The network as a whole is not listed.

No DROP prefixes None of its announced space is on the DROP prefix list.

Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 454 networks and 1,852 prefixes, as published 2026-11-08. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.

FBI IC3

No IC3 indicators Nothing from the FBI IC3 feed.

IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.

Elsewhere

Cross-check