139.140.0.0/17
AS22847 · Bowdoin College
Need more data or want to access it via API or data downloads? Sign up to get free access
Sign up for free ›Summary
| Country |
United States
|
| Domain | bowdoin.edu |
| ASN | AS22847 |
| Parent Range | 139.140.0.0/16 |
| Registry | ARIN |
| ID | BOWDOIN |
WHOIS Details
NetHandle: NET-139-140-0-0-1 OrgID: BOWDOI-1 Parent: NET-139-0-0-0-0 NetName: BOWDOIN NetRange: 139.140.0.0 - 139.140.255.255 NetType: allocation RegDate: 1990-03-16 Updated: 2024-03-15 TechHandle: SUMME231-ARIN Source: ARIN OrgID: BOWDOI-1 OrgName: Bowdoin College CanAllocate: Street: 9600 College Station City: Brunswick State/Prov: ME Country: US PostalCode: 04011 RegDate: 2001-12-04 Updated: 2024-11-25 OrgAdminHandle: NOC52-ARIN OrgTechHandle: NOC52-ARIN OrgTechHandle: SUMME231-ARIN OrgTechHandle: ZB120-ARIN OrgAbuseHandle: ZB120-ARIN Source: ARIN POCHandle: NOC52-ARIN IsRole: N LastName: Center FirstName: Network Street: 9600 College Station City: Brunswick State/Prov: ME Country: US PostalCode: 04011 RegDate: 2001-12-04 Updated: 2024-09-16 OfficePhone: +1-207-725-3641 Mailbox: noc@bowdoin.edu Source: ARIN POCHandle: ZB120-ARIN IsRole: Y LastName: NOC FirstName: Street: 9660 College Station City: Brunswick State/Prov: ME Country: US PostalCode: 04011 RegDate: 2002-06-06 Updated: 2024-09-16 OfficePhone: +1-207-725-3641 Mailbox: noc@bowdoin.edu Source: ARIN POCHandle: SUMME231-ARIN IsRole: N LastName: Summers FirstName: Bill Street: 255 Maine St City: Brunswick State/Prov: ME Country: US PostalCode: 04011 RegDate: 2024-03-15 Updated: 2024-03-15 OfficePhone: +1-207-725-3595 Mailbox: w.summers@bowdoin.edu Source: ARIN
Overlapping Ranges
BGP prefixes that contain 139.140.0.0/17
| Range | ASN | Company | Num of IPs |
|---|---|---|---|
| 139.140.0.0/16 | AS22847 | Bowdoin College | 65,536 |
Hosted domains
There is 1 domain name hosted across 1 IP address on this ASN. Checkout our API to access full domain hosting information.
| IP Address | Domain | Domains on this IP |
|---|
Hosted domains API
Pingable IPs
1,406 IPs in this range replied to an ICMP ping during our most recent internet scan. Learn more.
| IP Address | ASN | Details |
|---|---|---|
| 139.140.87.102 |
5.50ms from Providence,
US
|
|
| 139.140.109.84 |
5.30ms from Providence,
US
|
|
| 139.140.72.123 |
5.18ms from Providence,
US
|
|
| 139.140.66.8 |
5.33ms from Providence,
US
|
|
| 139.140.112.190 |
5.27ms from Providence,
US
|
|
| 139.140.76.209 |
5.29ms from Providence,
US
|
|
| 139.140.34.20 |
7.87ms from Providence,
US
|
|
| 139.140.98.103 |
5.38ms from Providence,
US
|
|
| 139.140.79.147 |
5.10ms from Providence,
US
|
|
| 139.140.90.205 |
5.27ms from Providence,
US
|
|
| 139.140.59.101 |
8.09ms from Providence,
US
|
|
| 139.140.110.163 |
5.23ms from Providence,
US
|
|
| 139.140.99.10 |
5.20ms from Providence,
US
|
|
| 139.140.118.146 |
5.33ms from Providence,
US
|
|
| 139.140.6.11 |
4.17ms from Boston,
US
|
|
| 139.140.86.5 |
5.20ms from Providence,
US
|
|
| 139.140.78.16 |
5.41ms from Providence,
US
|
|
| 139.140.39.47 |
7.46ms from Providence,
US
|
|
| 139.140.83.2 |
5.49ms from Providence,
US
|
|
| 139.140.9.32 |
5.28ms from Providence,
US
|
|
| 139.140.100.18 |
5.26ms from Providence,
US
|
|
| 139.140.108.111 |
5.25ms from Providence,
US
|
|
| 139.140.89.77 |
5.25ms from Providence,
US
|
|
| 139.140.50.166 |
7.99ms from Providence,
US
|
|
| 139.140.38.135 |
7.94ms from Providence,
US
|
Other Pingable IPs
Below is a random selection of 25 IPs that replied to an ICMP ping during our most recent internet scan.
| IP Address | ASN | Details |
|---|---|---|
| 87.212.26.1 |
3.94ms from Amsterdam,
NL
|
|
| 70.174.116.1 |
5.87ms from Ashburn,
US
|
|
| 143.59.115.129 |
4.78ms from Atlanta,
US
|
|
| 124.122.226.49 |
4.65ms from Bangkok,
TH
|
|
| 117.138.116.145 |
11.56ms from Beijing,
CN
|
|
| 4.79.7.81 |
0.35ms from Boston,
US
|
|
| 181.166.168.1 |
1.23ms from Buenos Aires,
AR
|
|
| 181.29.240.1 |
1.26ms from Buenos Aires,
AR
|
|
| 186.136.168.1 |
1.13ms from Buenos Aires,
AR
|
|
| 45.246.84.1 |
4.54ms from Cairo,
EG
|
|
| 75.181.19.1 |
9.59ms from Charlotte,
US
|
|
| 173.17.100.1 |
16.06ms from Chicago,
US
|
|
| 192.183.76.65 |
10.13ms from Chicago,
US
|
|
| 207.141.132.1 |
7.28ms from Chicago,
US
|
|
| 187.5.43.1 |
0.75ms from Curitiba,
BR
|
|
| 68.116.215.177 |
14.76ms from Dallas,
US
|
|
| 75.39.199.33 |
16.64ms from Dallas,
US
|
|
| 78.101.141.1 |
1.02ms from Doha,
QA
|
|
| 187.102.250.17 |
13.21ms from Fortaleza,
BR
|
|
| 27.39.224.1 |
11.84ms from Guangzhou,
CN
|
|
| 182.245.33.1 |
12.43ms from Guiyang,
CN
|
|
| 111.127.172.1 |
11.40ms from Hohhot,
CN
|
|
| 20.239.197.225 |
0.59ms from Hong Kong,
HK
|
|
| 118.143.19.81 |
0.88ms from Hong Kong,
HK
|
|
| 68.206.105.97 |
19.91ms from Houston,
US
|
Traceroute
Below is a recent traceroute taken from the IPinfo ProbeNet to an IP in this range. Learn more.
IPinfo ProbeNet
in Calgary, CA
What are IP address ranges?
IP address ranges, or netblocks, are groups of related IP addresses. They are usually represented as a base IP address, followed by a slash, and then a netmask which represents how many IP addresses are contained within the netblock. This format is known as CIDR. You'll also sometimes see netblocks given as a start ip address, and an end ip address, or an ip address range.
Traffic works its way around the internet based on the routing table, which contains a list of networks and their associated netblocks.
An API built with users in mind: reliable, accurate, and easy-to-use
Discover why industry-leading companies around the globe love our data. IPinfo's accurate insights fuel use cases from cybersecurity, data enrichment, web personalization, and much more.
Our IP tools
Explore all tools
Summarize IPs
Use our data visualization tool to create a visual overview of multiple IPs.
Try Summarize IPs