Skip to main content

AS203493

YACOLO-AS

--- GoodLine ---

Registry

Authoritative registration data

AS number
203493
Name
YACOLO-AS
Organisation
--- GoodLine ---
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

6

Total announced

11

Announced prefixes

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

Prefixes announced by AS203493
109.248.206.0/23 IPv4 /23 not checked
194.226.42.0/24 IPv4 /24 not checked
194.87.209.0/24 IPv4 /24 not checked
46.8.251.0/24 IPv4 /24 not checked
89.37.193.0/24 IPv4 /24 not checked
2a0d:d940:1200::/40 IPv6 /40 RPKI not found
2a0d:d940:1d00::/40 IPv6 /40 not checked
2a09:6280:3::/48 IPv6 /48 RPKI valid
2a0e:b107:2791::/48 IPv6 /48 RPKI valid
2a0e:b107:2792::/48 IPv6 /48 RPKI valid
2a0e:b107:2796::/48 IPv6 /48 RPKI valid

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 AS203493
Address families
SFO-IX: SFO-IX 10,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 AS203493 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS203493 in AS paths

Observed upstreams
Families
AS48858 Milecom-as 1,041 4,934
v4 v6
AS35598 INETCOM 469 1,206
v4
AS39927 Elight-AS 163 420
v4
AS13094 SFO-IX-AS 63 313
v4 v6
AS62255 BEMYLINK 82 280
v4
AS41327 FIBERTELECOM-AS 3 5
v4
AS31500 GNM-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS203493 in AS paths

Observed downstreams
Families
AS207713 GIR-AS 641 2,841
v4 v6
AS218462 254 333
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 8
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.