Whois查询
查询域名、IP或ASN的注册信息、到期时间、注册商等详细信息
注册信息
AS15544
AS名称
DATAWAYS
组织
DATAWAYS S.A.
注册时间
1970-01-01T00:00:00Z
更新时间
2024-11-13T16:05:15Z
注册人/组织
DATAWAYS S.A.
原始Whois信息
aut-num: AS15544 as-name: DATAWAYS descr: DATAWAYS S.A. descr: Thessaloniki, Greece descr: 27, Georgikis Scholis Ave. GR-57001 descr: Tel: +30.2310953953 descr: Fax: +30.2310953963 descr: Web: https://www.dataways.gr org: ORG-DHA1-RIPE remarks: remarks: remarks: --------------- AS15544 / DATAWAYS S.A. --------------- remarks: --------- PUBLIC IPv4/IPv6 BGP PEERING POLICY --------- remarks: remarks: 24x7 NOC Phone: +30.2310953966 remarks: remarks: remarks: General Info about DATAWAYS remarks: =========================== remarks: remarks: DATAWAYS is a multiprotocol internet service provider remarks: founded in 2000 by a team of IT professionals with many remarks: years of technical expertise and knowledge in the area remarks: of information technology and telecommunications. remarks: The company has offices in Athens and Thessaloniki. remarks: remarks: We provide IPv4/IPv6 transit with at least two major remarks: carriers in every location. We are also member of Greek remarks: Internet Exchange (GR-IX) and maintain peering agreements remarks: with other Greek major networks and members of GR-IX. remarks: remarks: We are ISO/IEC 27001:2013 certified and maintain a remarks: security policy according to Greek/EU laws. We are also remarks: a RIPE member since 2000 and we operate as a LIR. remarks: remarks: We use the RIPE database as the primary IRR database remarks: in which we register most of our objects. remarks: remarks: The as-set which contains our own AS number and all our remarks: customers' AS numbers is AS-DATAWAYS. Please use this remarks: as-set if you do prefix filtering, unless otherwise noted. remarks: remarks: Our PeeringDB record is at http://as15544.peeringdb.com remarks: remarks: remarks: General Peering Policy Info remarks: =========================== remarks: remarks: - We honor no-export and no-advertise well-known remarks: communities. remarks: remarks: - We do *NOT* honor the MED BGP attribute. All routes remarks: received from our upstreams, customers or IX-peers on both remarks: primary/backup routers get a metric of 0. Please see below remarks: about our primary/backup scheme. remarks: remarks: - bogon/martian prefixes are rejected on import. remarks: remarks: - Prefixes containing a bogon/reserved/private AS number remarks: in their as-path are rejected. remarks: remarks: - We reject the default-route prefix (0/0, ::/0) from all remarks: peers (upstreams/customers/IX-peers). remarks: remarks: - Prefixes longer than /24 for IPv4 or /48 for IPv6 remarks: are rejected. remarks: remarks: - We use BOTH prefix access lists and as-path access lists remarks: for prefix filtering. Customers or IX-peers imported remarks: prefixes must be registered with a valid route/route6 remarks: object in the RIPE database. The prefix must be originating remarks: from the customer's AS or, in case the peer is an IX-peer, remarks: the peer's AS and their adjacent AS if any. remarks: remarks: All other advertisements are rejected. remarks: remarks: Our filters are automatically updated every business-day remarks: morning. Contact [email protected] for an irregular update. remarks: remarks: remarks: Primary/Backup BGP Routers remarks: ========================== remarks: DATAWAYS prefers to connect with other autonomous systems remarks: using a cluster of bgp routers with at least two BGP remarks: sessions for redundancy. Each session originates from a remarks: different router. The first/primary session is maintained remarks: on our primary-designated router while any other secondary remarks: sessions use our backup(s) router(s). remarks: remarks: Routes received from our peers on the primary router always remarks: get a higher local preference than the backup router. remarks: remarks: Our customers can fine-tune our local-preference values remarks: using the appropriate community tags. See below. remarks: remarks: Routes advertised to our peers have their metric set to 0 remarks: on primary and 20 on backup. If the remote AS does not remarks: honor the MED attribute we follow the appropriate remarks: technique as instructed by the remote AS import policy. remarks: remarks: remarks: BGP Communities used by our Customers remarks: ===================================== remarks: Our customers can use the following communities to remarks: influence our BGP routers: remarks: remarks: as-path prepend: remarks: ---------------- remarks: 15544:5000 Prepend 5 times to all Upstreams remarks: 15544:5900 Prepend 5 times to all GR-IX Peers remarks: remarks: local-preference override: remarks: -------------------------- remarks: 15544:7090 Set local-preference of customer's prefix remarks: to very-low local-preference mode. remarks: remarks: In normal operations the customer's announcements have remarks: a higher local-preference value than IX-peers and remarks: upstreams announcements. remarks: remarks: The order is: [CUSTOMER] > [IX-PEERS] > [UPSTREAMS] remarks: remarks: If you tag your advertisements with 15544:7090 then remarks: the order changes to: remarks: remarks: [IX-PEERS] > [UPSTREAMS] > [CUSTOMER] remarks: remarks: In this mode, prefixes received from IX-peers and/or remarks: from our upstreams are more preferred. A multi-homed remarks: customer can utilize this mode to use us a remarks: backup/last resort path. remarks: remarks: remarks: Export Prefix Policy for our Customers remarks: ====================================== remarks: We advertise the following prefix-sets to our customers: remarks: remarks: FIRT: advertise the entire global BGP routing table remarks: remarks: GRIX: advertise only prefixes learned from our GR-IX peers. remarks: remarks: RIPE: advertise only the RIPE-NCC prefix. This is remarks: 193.0.0.0/21 for IPv4 and 2001:67c:2e8::/48 for IPv6 remarks: and they both originating from AS3333. remarks: remarks: default: advertise only the default route (0/0 or ::/0) remarks: remarks: Customer can select/change any of the above sets by remarks: e-mailing [email protected]. remarks: remarks: remarks: # END OF PUBLIC BGP PEERING POLICY FOR DATAWAYS remarks: remarks: Import/export policy in RPSL now follows. This is a remarks: generic description of our current peering plan. No remarks: strict filtering or local preference actions are remarks: described. Use only for reference. remarks: remarks: # UPSTREAMS remarks: mp-import: afi any from AS174 from AS3356 accept ANY; mp-export: afi any to AS174 to AS3356 announce AS-DATAWAYS AND <^AS15544+AS-DATAWAYS*$>; remarks: remarks: # GR-IX PEERS remarks: mp-import: afi any from PRNG-AS15544-GRIX-PEERS accept (PeerAS OR PeerAS:AS-TO-AIX) AND <^PeerAS+PeerAS:AS-TO-AIX*$>; mp-export: afi any to PRNG-AS15544-GRIX-PEERS announce AS15544:AS-TO-AIX AND <^AS15544+AS15544:AS-TO-AIX*$>; remarks: remarks: # CYTANET Cyprus peering in GR-IX remarks: mp-import: afi any from AS6866 accept AS-CYTANET AND <^AS6866+AS-CYTANET*$>; mp-export: afi any to AS25152 announce AS15544:AS-TO-AIX AND <^AS15544+AS15544:AS-TO-AIX*$>; remarks: remarks: # RIPE NCC K-ROOT Local Mirror in GR-IX remarks: mp-import: afi any from AS25152 accept RS-KROOT-GRNET AND <^AS25152*$>; mp-export: afi any to AS25152 announce AS15544 AND <^AS15544*$>; remarks: remarks: # VERISIGN J-ROOT/COM/NET Local Mirror in GR-IX remarks: mp-import: afi any from AS25152 accept AS26415 AND <^AS26415*$>; mp-export: afi any to AS25152 announce AS15544 AND <^AS15544*$>; remarks: remarks: # CUSTOMERS remarks: mp-import: afi any from AS199382 accept AS199382 AND <^AS199382*$>; mp-export: afi ipv4 to AS199382 announce { 0.0.0.0/0 }; mp-export: afi ipv6 to AS199382 announce { ::/0 }; mp-import: afi any from AS203780 accept AS203780 AND <^AS203780*$>; mp-export: afi ipv4 to AS203780 announce { 193.0.0.0/21 }; mp-export: afi ipv6 to AS203780 announce { 2001:67c:2e8::/48 }; mp-import: afi any from AS207062 accept AS207062 AND <^AS207062*$>; mp-export: afi ipv4 to AS207062 announce { 193.0.0.0/21 }; mp-export: afi ipv6 to AS207062 announce { 2001:67c:2e8::/48 }; mp-import: afi any from AS57335 accept AS57335 AND <^AS57335*$>; mp-export: afi ipv4 to AS57335 announce { 0.0.0.0/0 }; mp-export: afi ipv6 to AS57335 announce { ::/0 }; mp-import: afi any from AS214791 accept AS214791 AND <^AS214791*$>; mp-export: afi ipv4 to AS214791 announce any; mp-export: afi ipv6 to AS214791 announce any; remarks: admin-c: DUMY-RIPE tech-c: DUMY-RIPE status: ASSIGNED mnt-by: RIPE-NCC-END-MNT mnt-by: DWMR1-RIPE-MNT notify: [email protected] created: 1970-01-01T00:00:00Z last-modified: 2024-11-13T16:05:15Z source: RIPE remarks: **************************** remarks: * THIS OBJECT IS MODIFIED remarks: * Please note that all data that is generally regarded as personal remarks: * data has been removed from this object. remarks: * To view the original object, please query the RIPE Database at: remarks: * http://www.ripe.net/whois remarks: **************************** --- ARIN Whois --- # # ARIN WHOIS data and services are subject to the Terms of Use # available at: https://www.arin.net/resources/registry/whois/tou/ # # If you see inaccuracies in the results, please report at # https://www.arin.net/resources/registry/whois/inaccuracy_reporting/ # # Copyright 1997-2026, American Registry for Internet Numbers, Ltd. # No match found for a AS15544. # # ARIN WHOIS data and services are subject to the Terms of Use # available at: https://www.arin.net/resources/registry/whois/tou/ # # If you see inaccuracies in the results, please report at # https://www.arin.net/resources/registry/whois/inaccuracy_reporting/ # # Copyright 1997-2026, American Registry for Internet Numbers, Ltd. #