AS8315 - Accenture B. V.


Detailed information about the Autonomous System AS8315:

API Url https://api.ipapi.is/?q=AS8315
Status Active
Organization Accenture B. V.
Description ACNBB, NL
Website accenture.com
Type business
Abuse E-Mail abuse@cie.ac
Whois https://api.ipapi.is/?whois=AS8315
Created 2006-01-05
Updated 2023-05-31
Country NL

IPv4 Prefixes

Currently, there are 63 IPv4 prefixes for AS8315 - Accenture B. V. in the database. This amounts to 148,736 IPv4 addresses that are hosted on this ASN. The following list shows the first 25 IPv4 prefixes of the ASN. To obtain all prefixes, please purchase the full database

2.56.171.0/24
5.100.224.0/21
5.100.231.0/24
79.99.184.0/21
83.98.128.0/18
83.98.192.0/21
83.98.200.0/22
83.98.208.0/20
85.92.128.0/20
85.92.144.0/22
85.158.160.0/21
85.158.160.0/24
85.222.192.0/21
87.237.99.0/24
89.18.160.0/22
89.18.168.0/21
89.18.180.0/22
89.30.128.0/18
89.30.192.0/19
89.30.208.0/20
89.30.224.0/21
91.200.48.0/23
91.200.49.0/24
91.200.51.0/24
91.216.113.0/24

IPv6 Prefixes

Currently, there are 15 IPv6 prefixes for AS8315 - Accenture B. V. in the database. This amounts to 1,981,943,211,821,713,400,000,000,000,000 IPv6 addresses that are hosted on this ASN.

2001:678:76c::/48
2001:16f8::/32
2a00:1bd8::/32
2a01:40e0::/32
2a02:20b0::/32
2a02:20b1::/32
2a02:2858::/29
2a02:2858:200::/40
2a02:2858:300::/40
2a02:2858:400::/40
2a02:2858:500::/40
2a03:5500::/31
2a0d:5040::/29
2a0d:5040::/32
2a0d:5041::/32

Raw WHOIS Record - AS8315 - Accenture B. V.

as-block:       AS8192 - AS8523
descr:          RIPE NCC ASN block
remarks:        These AS Numbers are assigned to network operators in the RIPE NCC service region.
mnt-by:         RIPE-NCC-HM-MNT
created:        2018-11-22T15:27:23Z
last-modified:  2018-11-22T15:27:23Z
source:         RIPE



aut-num:        AS8315
as-name:        ACNBB
remarks:        Accenture Backbone
remarks:        https://www.accenture.com
remarks:        ==============================================================
remarks:        Please find our peering details at
remarks:        http://as8315.peeringdb.com/
remarks:        ==============================================================
remarks:        We have an open peering policy and would like to peer with
remarks:        you. Please send requests to noc@cie.ac.
remarks:        ==============================================================
remarks:        NOC: noc@cie.ac
remarks:        Abuse: dnsadmin@accenture.com
remarks:        ==============================================================
remarks:        We share the view that for many networks ( including ours:-) )
remarks:        only some abstraction of the actual routing policy should/can
remarks:        be published in the IRR.
remarks:        Right now we are abstracting to a very essential minimum.
remarks:        the most important and helpful use of the IRR is
remarks:        to publish what a network will announce to peers and upstream
remarks:        we are providing that by means of the AS-set AS8315:AS-SENTIA
remarks:        which we have been keeping up to date all the time
remarks:        we encourage all our neighbors to define and maintain an
remarks:        AS-set to describe their announcements, and to register
remarks:        all the routes (and have their customers do so as well)
import:         from AS-ANY accept ANY # heavy abstraction hits! well, we are ... neither peering promiscuously nor accepting all junk routes offered...
remarks:        we maintain a list of what our neighbors have told us
remarks:        about their announcements towards AS8315 - in terms of
remarks:        AS-set (preferred), AS number, route-set
remarks:        (and the IRR database used to publish)
remarks:        in fact we apply route filters based on this
remarks:        for all neighbors - as far as feasible
remarks:        for data published through the RIPE routing registry
remarks:        we generate filters automatically
remarks:        we consider the integration of RIR and routing registry data
remarks:        and the application of RPSS authorization a great feature
remarks:        of the RIPE routing registry
remarks:        unfortunately this benefit is not available with any
remarks:        other IRR database that we know of...
remarks:        and some of the IRR databases allow essentially any garbage
remarks:        to be registered without any control - making those databases
remarks:        quite useless...
export:         to AS8315:AS-ACNBB announce ANY # but don't publish that list; in general - if they ask for less, we can do
export:         to AS-ANY announce AS8315:AS-ACNBB # New AS SET
remarks:        customers are strongly encouraged to define and maintain
remarks:        an AS-set that we will include in the definition
remarks:        of AS8315:AS-ACNBB (if we are told the name)
remarks:        this will be sufficient to have our peers accept the routes
remarks:        in any case peers - and any network in the Internet -
remarks:        is free to apply some selective policy (e.g. prefix
remarks:        length based)
remarks:        but we do not think that any such selective policy
remarks:        will be based on details of our routing policy omitted
remarks:        from this aut-num: object
remarks:        unfortunately some customers do not provide usable IRR data;
remarks:        we will NOT add to the uncontrolled garbage in the IRR by
remarks:        proxy registering in some database that requires no
remarks:        authorization
remarks:        we advise customers that routes without IRR registration
remarks:        and not covered by AS8315:AS-ACNBB may receive less than
remarks:        full support by some of our peer networks and other
remarks:        parts of the Internet
remarks:        ==============================================================
remarks:        IPv6 we do/publish essentially the same like for IPv4
mp-import:      afi ipv6.unicast from AS-ANY accept ANY # heavy abstraction... neither peering promiscuously nor accepting all junk routes offered...
mp-export:      afi ipv6.unicast to AS8315:AS-ACNBB announce ANY # but don't publish that list; in general - if they ask for less, we can do
mp-export:      afi ipv6.unicast to AS-ANY announce AS8315:AS-ACNBB # for peers and others...
remarks:        ==============================================================
org:            ORG-ABV1-RIPE
admin-c:        ACN1337-RIPE
tech-c:         ACN1337-RIPE
abuse-c:        ABAR3-RIPE
status:         ASSIGNED
mnt-by:         RIPE-NCC-END-MNT
mnt-by:         ACNBB-MNT
created:        2006-01-05T09:59:28Z
last-modified:  2023-05-31T11:10:32Z
source:         RIPE

organisation:   ORG-ABV1-RIPE
org-name:       Accenture B. V.
country:        NL
org-type:       LIR
address:        201 East 4th Street, Suite1600
address:        45202
address:        Cincinnati, OH
address:        UNITED STATES
phone:          +15134551287
fax-no:         +13126527255
mnt-ref:        RIPE-NCC-HM-MNT
mnt-ref:        ACN-RIPE-IPV6-MNT
mnt-by:         RIPE-NCC-HM-MNT
mnt-by:         ACN-RIPE-IPV6-MNT
admin-c:        CEH5-RIPE
admin-c:        KP3355-RIPE
admin-c:        SJW12-RIPE
abuse-c:        AA26757-RIPE
created:        2012-09-28T14:18:53Z
last-modified:  2023-03-21T16:27:33Z
source:         RIPE # Filtered

role:           Accenture Backbone Role
address:        Gustav Mahlerplein 90
address:        1082MA Amsterdam
abuse-mailbox:  abuse@cie.ac
tech-c:         PL13771-RIPE
tech-c:         SK3127-RIPE
tech-c:         OvdL5-RIPE
nic-hdl:        ACN1337-RIPE
created:        2023-04-19T14:25:58Z
last-modified:  2023-05-31T12:46:49Z
source:         RIPE # Filtered
mnt-by:         ACNBB-MNT