Skip to main content

AS208892

DAINET-AS

ORG-SA635-RIPE

Registry

Authoritative registration data

AS number
208892
Name
DAINET-AS
Organisation
ORG-SA635-RIPE
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS208892
46.22.171.0/24 IPv4 /24 not checked
80.82.23.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 AS208892
Address families
EPIX.Warszawa 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 AS208892 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS208892 in AS paths

Observed upstreams
Families
AS62081 EPIX-WAW-GlobalMix 208 552
v4
AS42927 S-NET-AS 58 150
v4
AS24115 ASN-EQIX-MLPE 9 22
v4
AS201054 EPIX-PolMix 3 8
v4
AS137409 GSLNETWORKS-AS-AP 1 4
v4
AS9009 M247 1 2
v4
AS35320 ETT-AS 1 2
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS208892 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 14
v4
AS49544 i3Dnet 1 4
v4
AS36236 NETACTUATE 1 2
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.