Skip to main content

AS6325

ILLINOIS-CENTURY

Illinois Century Network

Registry

Authoritative registration data

AS number
6325
Name
ILLINOIS-CENTURY
Organisation
Illinois Century Network
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

56

IPv6 prefixes

5

Total announced

61

Announced prefixes

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

Prefixes announced by AS6325
207.63.0.0/16 IPv4 /16 RPKI valid
209.174.0.0/16 IPv4 /16 not checked
209.175.0.0/16 IPv4 /16 not checked
209.7.0.0/16 IPv4 /16 RPKI valid
216.124.0.0/16 IPv4 /16 RPKI valid
216.125.0.0/16 IPv4 /16 not checked
64.107.0.0/16 IPv4 /16 not checked
66.99.0.0/16 IPv4 /16 RPKI valid
163.191.0.0/17 IPv4 /17 RPKI not found
163.191.128.0/17 IPv4 /17 not checked
206.166.0.0/17 IPv4 /17 not checked
207.63.0.0/17 IPv4 /17 RPKI valid
207.63.128.0/17 IPv4 /17 not checked
209.174.0.0/17 IPv4 /17 RPKI valid
209.174.128.0/17 IPv4 /17 RPKI valid
209.175.0.0/17 IPv4 /17 RPKI valid
209.175.128.0/17 IPv4 /17 RPKI valid
209.7.0.0/17 IPv4 /17 not checked
209.7.128.0/17 IPv4 /17 RPKI valid
216.124.0.0/17 IPv4 /17 RPKI valid
216.124.128.0/17 IPv4 /17 not checked
216.125.0.0/17 IPv4 /17 not checked
216.125.128.0/17 IPv4 /17 RPKI valid
64.107.0.0/17 IPv4 /17 RPKI valid
64.107.128.0/17 IPv4 /17 not checked
64.150.0.0/17 IPv4 /17 not checked
65.79.0.0/17 IPv4 /17 RPKI valid
66.158.0.0/17 IPv4 /17 not checked
66.99.0.0/17 IPv4 /17 not checked
66.99.128.0/17 IPv4 /17 not checked
72.3.0.0/17 IPv4 /17 RPKI valid
206.166.0.0/18 IPv4 /18 RPKI valid
206.166.64.0/18 IPv4 /18 RPKI valid
207.63.0.0/18 IPv4 /18 not checked
207.63.128.0/18 IPv4 /18 RPKI valid
207.63.192.0/18 IPv4 /18 not checked
207.63.64.0/18 IPv4 /18 RPKI valid
209.175.0.0/18 IPv4 /18 RPKI valid
209.175.128.0/18 IPv4 /18 RPKI valid
209.175.192.0/18 IPv4 /18 RPKI valid
209.175.64.0/18 IPv4 /18 RPKI valid
209.7.0.0/18 IPv4 /18 not checked
209.7.128.0/18 IPv4 /18 RPKI valid
209.7.192.0/18 IPv4 /18 RPKI valid
209.7.64.0/18 IPv4 /18 RPKI valid
216.124.128.0/18 IPv4 /18 RPKI valid
216.124.192.0/18 IPv4 /18 not checked
216.125.192.0/18 IPv4 /18 not checked
64.107.0.0/18 IPv4 /18 RPKI valid
64.107.128.0/18 IPv4 /18 RPKI valid
64.107.192.0/18 IPv4 /18 not checked
64.107.64.0/18 IPv4 /18 RPKI valid
66.99.0.0/18 IPv4 /18 RPKI valid
66.99.128.0/18 IPv4 /18 not checked
66.99.192.0/18 IPv4 /18 RPKI valid
66.99.64.0/18 IPv4 /18 not checked
2001:1848::/32 IPv6 /32 not checked
2001:1848:4000::/34 IPv6 /34 RPKI valid
2001:1848:8000::/34 IPv6 /34 not checked
2001:1848:c000::/34 IPv6 /34 RPKI valid
2001:1848:1000::/36 IPv6 /36 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 AS6325
Address families
Equinix Chicago 200,000 Mbps IPv4 · IPv6
FD-IX - St. Louis: Main 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 AS6325 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS6325 in AS paths

Observed upstreams
Families
AS174 COGENT-174 3,483 11,035
v4 v6
AS6461 ZAYO-6461 535 5,306
v4 v6
AS6939 HURRICANE 487 1,594
v4 v6
AS22335 MREN 160 766
v4 v6
AS7018 ATT-INTERNET4 265 649
v4 v6
AS293 ESNET 22 56
v4

No rows match “”.

Showing – of

Observed downstreams

43 networks seen after AS6325 in AS paths

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS19151 BBO-1 20 108
v4
AS49544 i3Dnet 19 53
v4 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.