1,465 Works

internet_outage_adaptive_a36all-20190401 (2019-04-01 to 2019-07-01)

Combined reachability information for over 3.5M /24 subnets; this dataset is created by post-processing data from datasets internet_outage_adaptive_a36c-20190401 internet_outage_adaptive_a36e-20190401 internet_outage_adaptive_a36g-20190401 internet_outage_adaptive_a36j-20190401 internet_outage_adaptive_a36n-20190401 internet_outage_adaptive_a36w-20190401

internet_outage_adaptive_a37w-20190701 (2019-07-01 to 2019-10-01)

To collect this data, all allocated and responsive Internet IP address blocks were pinged by sending ICMP ECHO_REQUEST (PING) packet. The block status was recorded in this data set. Probe was repeated every 11 minutes, and more quickly when uncertain about block status. In all, approximately 3.5M /24 subnets were periodically probed.

internet_outage_adaptive_a37j-20190701 (2019-07-01 to 2019-10-01)

To collect this data, all allocated and responsive Internet IP address blocks were pinged by sending ICMP ECHO_REQUEST (PING) packet. The block status was recorded in this data set. Probe was repeated every 11 minutes, and more quickly when uncertain about block status. In all, approximately 3.5M /24 subnets were periodically probed.

internet_outage_adaptive_a37c-20190701 (2019-07-01 to 2019-10-01)

To collect this data, all allocated and responsive Internet IP address blocks were pinged by sending ICMP ECHO_REQUEST (PING) packet. The block status was recorded in this data set. Probe was repeated every 11 minutes, and more quickly when uncertain about block status. In all, approximately 3.5M /24 subnets were periodically probed.

internet_outage_adaptive_a38all-20191001 (2019-10-01 to 2020-01-01)

Combined reachability information for over 3.5M /24 subnets; this dataset is created by post-processing data from datasets internet_outage_adaptive_a38c-20191001 internet_outage_adaptive_a38e-20191001 internet_outage_adaptive_a38g-20191001 internet_outage_adaptive_a38j-20191001 internet_outage_adaptive_a38n-20191001 internet_outage_adaptive_a38w-20191001

internet_outage_adaptive_a37e-20190701 (2019-07-01 to 2019-09-05)

To collect this data, all allocated and responsive Internet IP address blocks were pinged by sending ICMP ECHO_REQUEST (PING) packet. The block status was recorded in this data set. Probe was repeated every 11 minutes, and more quickly when uncertain about block status. In all, approximately 3.5M /24 subnets were periodically probed.

internet_address_survey_reprobing_it91c-20200730 (2020-07-30 to 2020-08-13)

internet_address_census_it88e-20191127 (2019-11-27 to 2019-12-29)

To collect this data, an Internet-wide IP address sweep was conducted. Every IP address in the ranges allocated by IANA was pinged once by sending ICMP ECHO_REQUEST (PING) packet. If the response (ICMP_ECHO_REPLY) came, its IP address was recorded in this data-set. In all, over 2.5 billion distinct IP addresses were probed during this experiment.

internet_address_census_it90c-20200428 (2020-04-28 to 2020-05-30)

internet_outage_adaptive_a39e-20200101 (2020-01-01 to 2020-04-01)

To collect this data, all allocated and responsive Internet IP address blocks were pinged by sending ICMP ECHO_REQUEST (PING) packet. The block status was recorded in this data set. Probe was repeated every 11 minutes, and more quickly when uncertain about block status. In all, approximately 3.5M /24 subnets were periodically probed.

internet_address_census_it91n-20200710 (2020-07-10 to 2020-08-11)

internet_address_census_it91j-20200710 (2020-07-10 to 2020-08-11)

internet_outage_adaptive_a40c-20200401 (2020-04-01 to 2020-07-01)

internet_outage_adaptive_a40j-20200401 (2020-04-01 to 2020-07-01)

Active Topology Measurements with Skitter (07/15/1998 to 02/08/2008)

UCSD-Center For Applied Internet Data Analysis
Skitter is a tool for actively probing the Internet in order to analyze topology and performance. The skitter dataset contains forward IP paths from a source to many destinations, round trip times (RTT). The data can be used to track persistent routing changes, and to visualize network connectivity.

equinix-sin.woodynet.pch.net (05/25/2005 to 10/26/2008)

Packet Clearing House
This database encompasses daily 'sh ip bgp' formatted snapshots of the routing information base (RIB) for router amsix.equinix-sin.woodynet.pch.net, which is located at the Equinix Internet Business Exchange in Singapore. The routing topology depicted herein encompasses routes that have been exchanged between PCH and local peers that have agreed to share routing topology data for reseach purposes. Note that the scope of routing topology data captured in this data set will change constantly, as network conditions...

laiix.woodynet.pch.net (05/22/2005 to 10/26/2008)

Packet Clearing House
This database encompasses daily 'sh ip bgp' formatted snapshots of the routing information base (RIB) for router amsix.woodynet.pch.net, which is located at the LAIIX Internet Exchange in Los Angeles, California, USA. The routing topology depicted herein encompasses routes that have been exchanged between PCH and local peers that have agreed to share routing topology data for reseach purposes. Note that the scope of routing topology data captured in this data set will change constantly, as...

netnod.woodynet.pch.net (05/25/2005 to 10/26/2008)

Packet Clearing House
This database encompasses daily 'sh ip bgp' formatted snapshots of the routing information base (RIB) for router netnod.woodynet.pch.net, which is located at the NETNOD Internet Exchange in Stockholm, Sweden. The routing topology depicted herein encompasses routes that have been exchanged between PCH and local peers that have agreed to share routing topology data for reseach purposes. Note that the scope of routing topology data captured in this data set will change constantly, as network conditions...

npix.woodynet.pch.net (05/21/2005 to 10/26/2008)

Packet Clearing House
This database encompasses daily 'sh ip bgp' formatted snapshots of the routing information base (RIB) for router npix.woodynet.pch.net, which is located at the Nepal Internet Exchange in Kathmandu, Nepal. The routing topology depicted herein encompasses routes that have been exchanged between PCH and local peers that have agreed to share routing topology data for reseach purposes. Note that the scope of routing topology data captured in this data set will change constantly, as network conditions...

ims-dabber (05/09/2004 to 05/29/2004)

University Of Michigan
Anonymized packet traces for TCP destination port 5554, from May 9, 2004 to May 29, 2004 collected at the University of Michigan/Merit IMS sensors.

ims-tcp6101_veritas (01/10/2005 to 01/17/2005)

University Of Michigan
Anonymized packet traces for TCP destination port 6101, from Jan 10, 2005 to Jan 17, 2005 collected at the University of Michigan/Merit IMS sensors.

internet_address_survey_it12w-20060413 (04/13/2006 to 05/06/2006)

University Of Southern California-Information Sciences Institute
To collect this data, an Internet-wide IP address sweep was conducted. Every IP address in the ranges allocated by IANA was pinged once by sending ICMP ECHO_REQUEST (PING) packet. If the response (ICMP_ECHO_REPLY) came, its IP address was recorded in this data-set. In all, over 2.5 billion distinct IP addresses were probed during this experiment.

internet_address_survey_it13e-20060711 (07/11/2006 to 08/11/2006)

University Of Southern California-Information Sciences Institute
To collect this data, an Internet-wide IP address sweep was conducted. Every IP address in the ranges allocated by IANA was pinged once by sending ICMP ECHO_REQUEST (PING) packet. If the response (ICMP_ECHO_REPLY) came, its IP address was recorded in this data-set. In all, over 2.5 billion distinct IP addresses were probed during this experiment.

internet_address_survey_it13w-20060616 (06/16/2006 to 07/17/2006)

University Of Southern California-Information Sciences Institute
To collect this data, an Internet-wide IP address sweep was conducted. Every IP address in the ranges allocated by IANA was pinged once by sending ICMP ECHO_REQUEST (PING) packet. If the response (ICMP_ECHO_REPLY) came, its IP address was recorded in this data-set. In all, over 2.5 billion distinct IP addresses were probed during this experiment.

internet_address_survey_it15w-20061108 (11/08/2006 to 01/08/2007)

University Of Southern California-Information Sciences Institute
To collect this data, an Internet-wide IP address sweep was conducted. Every IP address in the ranges allocated by IANA was pinged once by sending ICMP ECHO_REQUEST (PING) packet. If the response (ICMP_ECHO_REPLY) came, its IP address was recorded in this data-set. In all, over 2.5 billion distinct IP addresses were probed during this experiment.

Registration Year

  • 2020
    79
  • 2019
    276
  • 2018
    319
  • 2017
    791

Resource Types

  • Dataset
    1,465