Skip to main content

AS3130

RGNET-SEA

RGnet Seattle Westin

Registry

Authoritative registration data

AS number
3130
Name
RGNET-SEA
Organisation
RGnet Seattle Westin
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS3130
147.28.0.0/23 IPv4 /23 not checked
192.83.230.0/24 IPv4 /24 not checked
198.180.153.0/24 IPv4 /24 not checked
2001:418:1::/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 AS3130
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 AS3130 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS3130 in AS paths

Observed upstreams
Families
AS2914 NTT-DATA-2914 120 300
v4 v6
AS174 COGENT-174 127 271
v4 v6
AS6939 HURRICANE 114 176
v4 v6
AS2497 IIJ 25 89
v4 v6
AS9002 RETN-AS 5 12
v4 v6
AS7575 AARNET-AS-AP 2 4
v4
AS52025 PARADOXNETWORKS-LIMITED 2 4
v4
AS394256 CLOUDSINGULARITY 1 4
v4 v6

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS3130 in AS paths

Observed downstreams
Families
AS25819 COLLIER-TECHNOLOGIES-LLC 125 184
v4 v6
AS32150 BRADFITZ-DANGA 19 30
v4 v6
AS47065 PEERING-RESEARCH-TESTBED-USC-UFMG-AS47065 11 14
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 23
v4 v6
AS35280 F5 2 4
v4
AS49544 i3Dnet 1 4
v4 v6
AS18106 VIEWQWEST-SG-AP 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.