Skip to main content

AS36243

BPS-NETWORKS

BPS Networks

Registry

Authoritative registration data

AS number
36243
Name
BPS-NETWORKS
Organisation
BPS Networks
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS36243
74.91.64.0/20 IPv4 /20 not checked
139.60.156.0/22 IPv4 /22 not checked
205.201.48.0/23 IPv4 /23 not checked
74.91.72.0/24 IPv4 /24 not checked
74.91.74.0/24 IPv4 /24 not checked
2602:ff87::/32 IPv6 /32 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS36243
Address families
FD-IX - St. Louis: Main 10,000 Mbps IPv4 · IPv6
STLIX: Main 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS36243 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS36243 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 228 1,448
v4 v6
AS6939 HURRICANE 229 459
v4 v6
AS19754 21 111
v4 v6
AS32097 WII 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS36243 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS1003 ANDREWNET 1 5
v4

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.