Skip to main content

AS33071

ISC-F-AS

Internet Systems Consortium, Inc.

Registry

Authoritative registration data

AS number
33071
Name
ISC-F-AS
Organisation
Internet Systems Consortium, Inc.
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS33071
199.6.0.0/24 IPv4 /24 not checked
2001:500:71::/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 AS33071
Address families
Equinix Chicago 1,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 AS33071 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS33071 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 553 4,183
v4 v6
AS1299 TWELVE99 81 297
v4 v6
AS6453 AS6453 21 51
v4 v6
AS137409 GSLNETWORKS-AS-AP 2 5
v4

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS33071 in AS paths

Observed downstreams
Families
AS24406 305 3,784
v4 v6
AS3557 47 101
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS19151 BBO-1 2 29
v4 v6
AS24482 SGGS-AS-AP 2 21
v4 v6
AS49544 i3Dnet 2 16
v4 v6
AS35280 F5 2 12
v4
AS36236 NETACTUATE 2 6
v4
AS1828 UNITAS 1 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.