Skip to main content

AS3245

DIGSYS-AS

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

Registry

Authoritative registration data

AS number
3245
Name
DIGSYS-AS
Organisation
------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

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

Prefixes announced by AS3245
193.68.128.0/17 IPv4 /17 not checked
193.68.0.0/19 IPv4 /19 not checked
193.68.96.0/19 IPv4 /19 not checked
185.143.80.0/22 IPv4 /22 not checked
192.92.129.0/24 IPv4 /24 not checked
2a02:6a80::/32 IPv6 /32 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 AS3245
Address families
B-IX 10,000 Mbps IPv4 · IPv6
BIX.BG: Main 10,000 Mbps IPv4 · IPv6
NetIX: NetIX 1,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 AS3245 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS3245 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 528 2,128
v4 v6
AS57344 372 1,605
v4 v6
AS8866 VIVACOM-AS 31 119
v4 v6
AS174 COGENT-174 41 117
v4 v6
AS57463 69 105
v6
AS50673 8 14
v6
AS3303 SWISSCOM 4 12
v4
AS137409 GSLNETWORKS-AS-AP 3 10
v4
AS59900 Balkan-Internet-Exchange 3 8
v4 v6
AS58057 SECUREBIT 4 7
v6
AS34019 HIVANE 4 6
v6
AS48646 4 6
v6
AS29632 NASSIST-AS 3 4
v6
AS401753 2 3
v6
AS8298 IPNG 2 2
v6

No rows match “”.

Showing of

Observed downstreams

5 networks seen after AS3245 in AS paths

Observed downstreams
Families
AS42909 164 838
v4 v6
AS197997 96 511
v4 v6
AS212442 290 392
v4
AS215888 142 184
v4
AS6939 HURRICANE 46 54
v6

No rows match “”.

Showing of

Uncertain adjacencies

25 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.