asn.dev

Autonomous system

AS11138 BEK-COMMUNICATIONS-INTERNET-ROUTER - BEK Communications Cooperative

Residential ARIN

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

Summary

BEK Communications Cooperative

United States · AI-generated

isp legacy

BEK-COMMUNICATIONS-INTERNET-ROUTER is the AS of BEK Communications Cooperative, a member-owned rural telephone and broadband cooperative headquartered in Steele, North Dakota. Founded in 1952 by subscribers in Burleigh, Emmons and Kidder counties — the "B-E-K" of the name — it now serves roughly 11,000 customers across a dozen central-ND counties with fiber internet, voice and TV.

What it's used for

An eyeball access network. RIS observes 56 announced IPv4 prefixes carrying about 18,944 addresses, no IPv6, and a single observed BGP neighbour: a co-op buying transit, not selling it. The address count lines up closely with the subscriber count, which is what a residential access network looks like when nearly every customer is a household or a small-town business.

Notable

The reverse DNS settles the classification. Sampled addresses across five different announced blocks all resolve under bektel.com, and the naming is generic access-pool naming — static-240-5.bektel.com, dhcp-75-133.bektel.com, and plain 64.202.36.5.bektel.com style records. Static and DHCP labels describe the assignment mechanism, not the customer, but a network whose PTRs are wall-to-wall first-party pools with an occasional business mail host (mail.feiinc.com) sitting in the middle of them is carrying subscribers, not servers.

Interesting

Every prefix the pack could resolve is registered to a BEK-* handle — BEK-64-31-240-0, BEK-142-44-8-0, and so on. The inventory is scattered across six unrelated-looking /8s (64.31, 64.202, 69.84, 64.38, 104.152, 142.44, 208.85), the accumulated result of years of small ARIN allocations, but every one of them is self-registered with first-party rDNS. That is the honest version of an untidy network, and it is exactly what distinguishes it from an AS announcing space registered to third parties.

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

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

ASNetworkPaths seen
AS26794Dakota Carrier Network3,762

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-03, 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 10 prefixes · 19.20K addresses IPv6 0 prefixes

CountryNamePrefixes
USUnited States of America10

Registry

Allocation record

ARIN · via Atlas (registry + RDAP)
Registry
ARIN
Handle
AS11138
Registry name
BEK-COMMUNICATIONS-INTERNET-ROUTER
Registrant
BEK Communications Cooperative
Abuse contact
abuse@bektel.com
Registered
2005-05-05
Last changed
2022-01-11
Allocation
assigned

Routing security

RPKI and IRR

Full detail
RPKI
2% valid · 1 valid, 56 with no ROA
ROAs
1 authorising AS11138
ASPA
no ASPA record
IRR
100% registered · 57 of 57 announcements
Route objects
15 naming AS11138

Reputation

Classification and threat

Residential Fixed-line consumer ISP. Addresses here are homes.

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: 451 networks and 1,853 prefixes, as published 2026-11-04. 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