Skip to main content

AS53340

FIBERHUB

VegasNAP, LLC

Registry

Authoritative registration data

AS number
53340
Name
FIBERHUB
Organisation
VegasNAP, LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

43

IPv6 prefixes

8

Total announced

51

Announced prefixes

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

Prefixes announced by AS53340
206.191.192.0/19 IPv4 /19 not checked
162.251.232.0/22 IPv4 /22 RPKI valid
162.251.236.0/22 IPv4 /22 RPKI valid
199.47.208.0/22 IPv4 /22 RPKI valid
64.112.60.0/22 IPv4 /22 not checked
104.143.10.0/23 IPv4 /23 not checked
104.225.250.0/23 IPv4 /23 RPKI valid
172.93.0.0/23 IPv4 /23 not checked
192.228.100.0/23 IPv4 /23 RPKI valid
192.228.108.0/23 IPv4 /23 RPKI valid
192.228.96.0/23 IPv4 /23 RPKI valid
76.164.234.0/23 IPv4 /23 not checked
102.129.131.0/24 IPv4 /24 not checked
102.165.18.0/24 IPv4 /24 not checked
104.225.134.0/24 IPv4 /24 not checked
147.189.133.0/24 IPv4 /24 RPKI valid
154.16.176.0/24 IPv4 /24 not checked
162.249.226.0/24 IPv4 /24 RPKI valid
172.93.1.0/24 IPv4 /24 not checked
176.111.222.0/24 IPv4 /24 RPKI valid
181.214.47.0/24 IPv4 /24 RPKI valid
181.214.81.0/24 IPv4 /24 not checked
181.214.87.0/24 IPv4 /24 RPKI valid
185.143.240.0/24 IPv4 /24 not checked
191.96.178.0/24 IPv4 /24 RPKI valid
191.96.179.0/24 IPv4 /24 RPKI valid
192.154.200.0/24 IPv4 /24 not checked
192.228.105.0/24 IPv4 /24 RPKI valid
192.228.106.0/24 IPv4 /24 RPKI valid
192.228.109.0/24 IPv4 /24 RPKI valid
193.160.70.0/24 IPv4 /24 RPKI not found
193.8.194.0/24 IPv4 /24 RPKI valid
199.127.56.0/24 IPv4 /24 not checked
199.43.206.0/24 IPv4 /24 RPKI valid
204.144.59.0/24 IPv4 /24 RPKI valid
204.77.6.0/24 IPv4 /24 RPKI valid
208.95.255.0/24 IPv4 /24 not checked
45.10.22.0/24 IPv4 /24 RPKI valid
5.182.50.0/24 IPv4 /24 RPKI valid
66.253.123.0/24 IPv4 /24 not checked
8.23.72.0/24 IPv4 /24 not checked
80.76.47.0/24 IPv4 /24 not checked
83.150.219.0/24 IPv4 /24 RPKI valid
2604:2280::/36 IPv6 /36 RPKI valid
2604:2280:d000::/36 IPv6 /36 RPKI valid
2604:2280:4000::/40 IPv6 /40 RPKI valid
2604:2280:4100::/40 IPv6 /40 RPKI valid
2604:2280::/40 IPv6 /40 RPKI valid
2604:2280:ff00::/40 IPv6 /40 RPKI valid
2604:2280:fffe::/48 IPv6 /48 RPKI valid
2606:6680:5::/48 IPv6 /48 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 AS53340
Address families
SIX Seattle: MTU 1500 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 AS53340 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS53340 in AS paths

Observed upstreams
Families
AS53667 PONYNET 1,915 23,709
v4
AS6939 HURRICANE 1,553 5,179
v4 v6
AS18530 ISOMEDIA-1 204 261
v4
AS137409 GSLNETWORKS-AS-AP 4 4
v4
AS9002 RETN-AS 3 4
v4 v6
AS394256 CLOUDSINGULARITY 1 2
v4 v6
AS7575 AARNET-AS-AP 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS53340 in AS paths

Observed downstreams
Families
AS397373 H4Y-TECHNOLOGIES 776 4,167
v4 v6
AS399804 HOSTODO 728 2,953
v4 v6
AS200019 AlexHost 511 1,502
v4 v6
AS36114 VERSAWEB 747 1,123
v4 v6
AS398304 THE-IT-GUY 156 226
v4

No rows match “”.

Showing – of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 14
v4 v6
AS49544 i3Dnet 1 4
v4 v6
AS36236 NETACTUATE 1 2
v4 v6
AS1828 UNITAS 1 1
v6
AS18106 VIEWQWEST-SG-AP 1 1
v4
AS34927 iFog-GmbH 1 1
v4
AS35280 F5 1 1
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.