View

You shouldnt be able to see this, But here lies a quick hack to make the super LG work

---

How are upstreams and downstreams calculated?

Upstreams

	ASN	Description
	AS16509	Amazon.com, Inc.

---

Peers

	ASN	Description
	AS16509	Amazon.com, Inc.

NetHandle:      NET-162-219-8-0-1
OrgID:          ALIDA-1
Parent:         NET-162-0-0-0-0
NetName:        ALIDA
NetRange:       162.219.8.0 - 162.219.15.255
NetType:        allocation
OriginAS:       40341, 15290
RegDate:        2013-08-07
Updated:        2023-06-05
Source:         ARIN



OrgID:          ALIDA-1
OrgName:        Alida
CanAllocate:    
Street:         365 Bloor St E, 5th Floor
City:           Toronto
State/Prov:     ON
Country:        CA
PostalCode:     M4W 3L4
RegDate:        2022-02-02
Updated:        2022-02-13
OrgAbuseHandle: ABUSE4753-ARIN
OrgAdminHandle: HOSTM1965-ARIN
OrgTechHandle:  HOSTM1965-ARIN
Source:         ARIN





OrgAbuseHandle:       ABUSE4753-ARIN
OrgAbuseName:          Abuse
# Email removed, Log into to bgp.tools to see whois emails


OrgAdminHandle:       HOSTM1965-ARIN
OrgAdminName:          Hostmaster
# Email removed, Log into to bgp.tools to see whois emails


OrgTechHandle:        HOSTM1965-ARIN
OrgTechName:           Hostmaster
# Email removed, Log into to bgp.tools to see whois emails

Last Update: 2023-11-28T05:54:56Z UTC / (Click here to force a refresh)

IRR Databases

IRR	Expected ASN
radb	AS14618	Show Raw route: 162.219.14.0/24 origin: AS14618 descr: Amazon EC2 Prefix mnt-by: MAINT-AS16509 source: radb changed: noc@amazon.com 20201112 #08:08:12
radb	AS16509	Show Raw route: 162.219.14.0/24 origin: AS16509 descr: Amazon EC2 Prefix mnt-by: MAINT-AS16509 source: radb changed: noc@amazon.com 20201112 #08:08:12