Skip to main content

AS19189

PULSEPOINT

Pulsepoint Inc

Registry

Authoritative registration data

AS number
19189
Name
PULSEPOINT
Organisation
Pulsepoint Inc
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

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

Prefixes announced by AS19189
74.214.192.0/24 IPv4 /24 not checked
74.214.193.0/24 IPv4 /24 not checked
74.214.194.0/24 IPv4 /24 not checked
74.214.195.0/24 IPv4 /24 not checked
74.214.196.0/24 IPv4 /24 not checked
74.214.197.0/24 IPv4 /24 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 AS19189
Address families
Equinix San Jose 10,000 Mbps IPv4
LINX NoVA 100,000 Mbps IPv4

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 AS19189 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS19189 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 259 948
v4
AS174 COGENT-174 185 450
v4
AS1299 TWELVE99 150 362
v4
AS6461 ZAYO-6461 69 224
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS19189 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 22
v4
AS49544 i3Dnet 1 4
v4

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.