Skip to main content

AS200478

TABOOLA-AS

Taboola.com ltd

Registry

Authoritative registration data

AS number
200478
Name
TABOOLA-AS
Organisation
Taboola.com ltd
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

15

IPv6 prefixes

2

Total announced

17

Announced prefixes

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

Prefixes announced by AS200478
185.106.32.0/22 IPv4 /22 not checked
141.226.224.0/23 IPv4 /23 not checked
141.226.124.0/24 IPv4 /24 not checked
141.226.127.0/24 IPv4 /24 not checked
141.226.224.0/24 IPv4 /24 not checked
141.226.225.0/24 IPv4 /24 not checked
141.226.226.0/24 IPv4 /24 not checked
141.226.227.0/24 IPv4 /24 not checked
141.226.228.0/24 IPv4 /24 not checked
141.226.229.0/24 IPv4 /24 not checked
141.226.230.0/24 IPv4 /24 not checked
185.106.32.0/24 IPv4 /24 not checked
185.106.33.0/24 IPv4 /24 not checked
185.106.34.0/24 IPv4 /24 not checked
185.106.35.0/24 IPv4 /24 not checked
2a06:3b80:110::/48 IPv6 /48 not checked
2a06:3b80:30::/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 AS200478
Address families
AMS-IX 10,000 Mbps IPv4
Equinix Chicago 10,000 Mbps IPv4
Equinix Los Angeles 10,000 Mbps IPv4
Equinix Singapore 10,000 Mbps IPv4
Equinix Tokyo 10,000 Mbps IPv4
NYIIX New York 10,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 AS200478 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

50 networks seen before AS200478 in AS paths

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS200478 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

59 adjacencies that may be an artefact of collector peering

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.