Skip to main content

AS213317

SIEA

--------------------------------------------------------

Registry

Authoritative registration data

AS number
213317
Name
SIEA
Organisation
--------------------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS213317
185.167.252.0/24 IPv4 /24 not checked
2a10:7a80::/29 IPv6 /29 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

Networks seen next to AS213317 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

18 networks seen before AS213317 in AS paths

Observed upstreams
Families
AS25091 241 339
v4 v6
AS56987 208 257
v4 v6
AS6939 18 19
v4
AS12779 2 9
v4 v6
AS9002 2 6
v6
AS20764 5 5
v4
AS6057 2 4
v4 v6
AS35280 2 4
v4 v6
AS8298 2 3
v4 v6
AS39351 2 3
v4 v6
AS41327 2 3
v4 v6
AS6758 1 2
v4 v6
AS39801 1 2
v4 v6
AS60171 1 2
v4 v6
AS4455 1 1
v4
AS7713 1 1
v4
AS20766 1 1
v4
AS43100 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS213317 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

26 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8218 1 7
v6
AS34019 1 6
v4 v6
AS24482 1 5
v4 v6
AS8529 1 4
v4 v6
AS49544 1 4
v4 v6
AS50628 1 4
v4 v6
AS25160 1 3
v4 v6
AS513 1 2
v4 v6
AS1828 1 2
v4 v6
AS2027 1 2
v4 v6
AS15547 1 2
v4
AS16347 1 2
v4 v6
AS20932 1 2
v4 v6
AS29075 1 2
v4 v6
AS34177 1 2
v4 v6
AS34288 1 2
v4 v6
AS35426 1 2
v4 v6
AS35600 1 2
v4 v6
AS36236 1 2
v4 v6
AS44097 1 2
v4 v6
AS49434 1 2
v4 v6
AS51185 1 2
v4 v6
AS58308 1 2
v4 v6
AS209823 1 2
v4 v6
AS13237 1 1
v4
AS35360 1 1
v6

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.