Skip to main content

AS2544

METRO-AS

King County Gov

Registry

Authoritative registration data

AS number
2544
Name
METRO-AS
Organisation
King County Gov
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

22

IPv6 prefixes

0

Total announced

22

Announced prefixes

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

Prefixes announced by AS2544
146.129.0.0/16 IPv4 /16 not checked
146.129.0.0/17 IPv4 /17 not checked
146.129.128.0/18 IPv4 /18 not checked
146.129.192.0/19 IPv4 /19 not checked
146.129.224.0/20 IPv4 /20 not checked
146.129.240.0/24 IPv4 /24 not checked
146.129.241.0/24 IPv4 /24 not checked
146.129.242.0/24 IPv4 /24 not checked
146.129.243.0/24 IPv4 /24 not checked
146.129.244.0/24 IPv4 /24 not checked
146.129.245.0/24 IPv4 /24 not checked
146.129.246.0/24 IPv4 /24 not checked
146.129.247.0/24 IPv4 /24 not checked
146.129.248.0/24 IPv4 /24 not checked
146.129.249.0/24 IPv4 /24 not checked
146.129.250.0/24 IPv4 /24 not checked
146.129.251.0/24 IPv4 /24 not checked
146.129.252.0/24 IPv4 /24 not checked
146.129.253.0/24 IPv4 /24 not checked
146.129.254.0/24 IPv4 /24 not checked
146.129.255.0/24 IPv4 /24 not checked
198.49.222.0/24 IPv4 /24 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 AS2544
Address families
SIX Seattle: MTU 1500 200,000 Mbps IPv4

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 AS2544 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS2544 in AS paths

Observed upstreams
Families
AS174 COGENT-174 1,774 9,156
v4
AS6939 HURRICANE 308 1,486
v4
AS14361 HOPONE-GLOBAL 111 663
v4
AS18530 ISOMEDIA-1 104 148
v4
AS9002 RETN-AS 30 117
v4
AS137409 GSLNETWORKS-AS-AP 26 86
v4
AS394256 CLOUDSINGULARITY 10 38
v4
AS7575 AARNET-AS-AP 9 37
v4
AS52025 PARADOXNETWORKS-LIMITED 6 12
v4

No rows match “”.

Showing – of

Observed downstreams

8 networks seen after AS2544 in AS paths

Observed downstreams
Families
AS33348 PIERCE-COUNTY 591 1,830
v4
AS32148 KCLS 503 989
v4
AS30198 KENT-SCHOOL-DISTRICT 259 898
v4
AS399987 TACOMA-PIERCE-COUNTY-HEALTH-DEPARTMENT 254 656
v4
AS396890 CITYOFREDMOND 250 328
v4
AS63432 PSRFA-ANS 249 328
v4
AS19014 NORCOM 36 48
v4
AS394640 TSD409-NET 33 40
v4

No rows match “”.

Showing – of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 10 407
v4
AS49544 i3Dnet 10 76
v4
AS35280 F5 10 38
v4
AS36236 NETACTUATE 10 38
v4
AS18106 VIEWQWEST-SG-AP 9 37
v4
AS34927 iFog-GmbH 4 26
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.