Skip to main content

AS7311

FRONTIER

Frontier Networks Inc

Registry

Authoritative registration data

AS number
7311
Name
FRONTIER
Organisation
Frontier Networks Inc
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

100

IPv6 prefixes

1

Total announced

101

Announced prefixes

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

Prefixes announced by AS7311
45.2.0.0/16 IPv4 /16 RPKI valid
216.126.64.0/19 IPv4 /19 not checked
24.104.160.0/20 IPv4 /20 not checked
24.146.112.0/20 IPv4 /20 not checked
24.146.64.0/20 IPv4 /20 RPKI valid
24.146.80.0/20 IPv4 /20 RPKI valid
67.21.144.0/20 IPv4 /20 RPKI valid
69.17.224.0/20 IPv4 /20 RPKI valid
69.17.240.0/20 IPv4 /20 RPKI valid
96.125.128.0/20 IPv4 /20 not checked
162.33.168.0/21 IPv4 /21 not checked
162.33.216.0/21 IPv4 /21 RPKI valid
192.154.144.0/21 IPv4 /21 not checked
192.154.152.0/21 IPv4 /21 RPKI valid
24.146.104.0/21 IPv4 /21 RPKI valid
38.143.48.0/21 IPv4 /21 not checked
45.2.192.0/21 IPv4 /21 not checked
96.125.128.0/21 IPv4 /21 RPKI valid
24.104.184.0/22 IPv4 /22 not checked
24.146.100.0/22 IPv4 /22 RPKI valid
24.146.96.0/22 IPv4 /22 RPKI valid
45.2.200.0/22 IPv4 /22 not checked
45.2.204.0/22 IPv4 /22 RPKI valid
96.125.136.0/22 IPv4 /22 RPKI valid
96.125.140.0/22 IPv4 /22 not checked
104.37.80.0/23 IPv4 /23 RPKI valid
104.37.82.0/23 IPv4 /23 not checked
162.33.180.0/23 IPv4 /23 RPKI valid
162.33.188.0/23 IPv4 /23 not checked
205.153.228.0/23 IPv4 /23 not checked
24.104.176.0/23 IPv4 /23 RPKI valid
24.104.180.0/23 IPv4 /23 RPKI valid
38.143.54.0/23 IPv4 /23 RPKI not found
45.2.208.0/23 IPv4 /23 not checked
45.2.210.0/23 IPv4 /23 not checked
45.2.220.0/23 IPv4 /23 not checked
45.2.224.0/23 IPv4 /23 RPKI valid
45.2.230.0/23 IPv4 /23 RPKI valid
161.129.186.0/24 IPv4 /24 RPKI valid
162.33.180.0/24 IPv4 /24 RPKI valid
162.33.181.0/24 IPv4 /24 not checked
204.138.4.0/24 IPv4 /24 RPKI not found
204.138.5.0/24 IPv4 /24 not checked
205.207.65.0/24 IPv4 /24 RPKI not found
206.204.110.0/24 IPv4 /24 not checked
216.126.64.0/24 IPv4 /24 not checked
216.126.71.0/24 IPv4 /24 not checked
216.126.72.0/24 IPv4 /24 RPKI valid
216.126.77.0/24 IPv4 /24 RPKI valid
216.126.79.0/24 IPv4 /24 not checked
216.126.86.0/24 IPv4 /24 not checked
216.126.88.0/24 IPv4 /24 RPKI valid
216.126.89.0/24 IPv4 /24 not checked
216.126.90.0/24 IPv4 /24 RPKI valid
216.126.91.0/24 IPv4 /24 not checked
216.126.92.0/24 IPv4 /24 RPKI valid
216.126.93.0/24 IPv4 /24 RPKI valid
216.126.94.0/24 IPv4 /24 not checked
216.126.95.0/24 IPv4 /24 RPKI valid
24.104.178.0/24 IPv4 /24 RPKI valid
24.104.179.0/24 IPv4 /24 RPKI valid
24.104.182.0/24 IPv4 /24 RPKI valid
24.104.183.0/24 IPv4 /24 not checked
24.104.188.0/24 IPv4 /24 not checked
24.104.189.0/24 IPv4 /24 not checked
24.104.190.0/24 IPv4 /24 not checked
24.104.191.0/24 IPv4 /24 RPKI valid
45.2.159.0/24 IPv4 /24 not checked
45.2.2.0/24 IPv4 /24 RPKI valid
45.2.207.0/24 IPv4 /24 RPKI valid
45.2.212.0/24 IPv4 /24 RPKI valid
45.2.214.0/24 IPv4 /24 RPKI valid
45.2.215.0/24 IPv4 /24 not checked
45.2.222.0/24 IPv4 /24 not checked
45.2.223.0/24 IPv4 /24 RPKI valid
45.2.226.0/24 IPv4 /24 RPKI valid
45.2.227.0/24 IPv4 /24 RPKI valid
45.2.228.0/24 IPv4 /24 not checked
45.2.232.0/24 IPv4 /24 RPKI valid
45.2.233.0/24 IPv4 /24 RPKI valid
45.2.236.0/24 IPv4 /24 not checked
45.2.238.0/24 IPv4 /24 not checked
45.2.239.0/24 IPv4 /24 not checked
45.2.24.0/24 IPv4 /24 RPKI valid
45.2.241.0/24 IPv4 /24 not checked
45.2.242.0/24 IPv4 /24 not checked
45.2.243.0/24 IPv4 /24 not checked
45.2.244.0/24 IPv4 /24 RPKI valid
45.2.245.0/24 IPv4 /24 not checked
45.2.246.0/24 IPv4 /24 RPKI valid
45.2.247.0/24 IPv4 /24 RPKI valid
45.2.248.0/24 IPv4 /24 RPKI valid
45.2.249.0/24 IPv4 /24 not checked
45.2.25.0/24 IPv4 /24 RPKI valid
45.2.254.0/24 IPv4 /24 RPKI valid
45.2.255.0/24 IPv4 /24 RPKI valid
45.2.68.0/24 IPv4 /24 RPKI valid
67.21.149.0/24 IPv4 /24 RPKI valid
67.21.159.0/24 IPv4 /24 RPKI valid
96.125.135.0/24 IPv4 /24 not checked
2605:8100::/32 IPv6 /32 RPKI valid

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 AS7311
Address families
Equinix New York 10,000 Mbps IPv4 · IPv6
NYIIX New York 10,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 1,000 Mbps IPv4 · IPv6
TorIX 20,000 Mbps IPv4 · IPv6
VANIX 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 AS7311 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

20 networks seen before AS7311 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 5,703 41,454
v4 v6
AS174 COGENT-174 1,387 7,782
v4
AS9002 RETN-AS 153 1,869
v4 v6
AS13030 INIT7 55 460
v4 v6
AS3356 LEVEL3 164 394
v4 v6
AS35280 F5 18 242
v4
AS33891 CORE-BACKBONE 12 196
v4
AS13786 SEABORN 28 168
v4
AS41327 FIBERTELECOM-AS 28 158
v4 v6
AS37468 ORG-AC4-AFRINIC 13 135
v4
AS394256 CLOUDSINGULARITY 14 119
v4 v6
AS6327 SHAW 10 111
v4
AS852 ASN852 59 94
v4
AS137409 GSLNETWORKS-AS-AP 5 65
v4
AS577 BACOM 14 47
v4
AS64049 RJIPL-SG 1 36
v4
AS7195 7195 3 28
v4
AS262761 ASN262761 1 19
v4
AS20473 AS-VULTR 2 2
v6
AS29838 AMC 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

31 networks seen after AS7311 in AS paths

No rows match “”.

Showing – of

Uncertain adjacencies

13 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 15 540
v4 v6
AS51185 MAINSTREAMING-AS 19 198
v4
AS22652 FIBRENOIRE-INTERNET 18 142
v4 v6
AS49544 i3Dnet 13 138
v4 v6
AS36236 NETACTUATE 12 118
v4 v6
AS835 GOCODEIT-EDGE 15 116
v4
AS52320 52320 23 109
v4 v6
AS21700 NEPTUNE-NETWORKS 21 104
v4
AS199524 GCORE 21 102
v4
AS61573 ASN61573 16 97
v4
AS18106 VIEWQWEST-SG-AP 3 28
v4
AS271253 ASN271253 3 28
v4
AS1403 EBOX 2 4
v6

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.