ResearchRouting table, RPKI, IRR & looking glass

AS3333 Reseaux IP Europeens Network Coordination Centre (RIPE NCC)

AS3333 (RIPE-NCC-AS) is registered to Reseaux IP Europeens Network Coordination Centre (RIPE NCC) in NL, through RIPE. It originates 8 prefixes in the global routing table.

6
IPv4 prefixes
2
IPv6 prefixes
4,608
IPv4 addresses
100%
RPKI valid

Who holds AS3333

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS3333
Handle
RIPE-NCC-AS
Organization
Reseaux IP Europeens Network Coordination Centre (RIPE NCC)
Country
NL
Registry
RIPE
ASPA
None published
WHOIS recordRIPE
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to 'AS3209 - AS3353'

as-block:       AS3209 - AS3353
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:19Z
last-modified:  2018-11-22T15:27:19Z
source:         RIPE

% Information related to 'AS3333'

% Abuse contact for 'AS3333' is 'abuse@ripe.net'

aut-num:        AS3333
as-name:        RIPE-NCC-AS
descr:          Reseaux IP Europeens Network Coordination Centre (RIPE NCC)
org:            ORG-RIEN1-RIPE
remarks:
remarks:
remarks:        ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
remarks:        | AS3333 RIPE-NCC-AS |
remarks:        | RIPE NCC (Network Coordination Centre) |
remarks:        ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
remarks:        | |
remarks:        | RIPE NCC (AS3333) operates an open peering policy: |
remarks:        | |
remarks:        | We advertise only routes from AS-RIPENCC |
remarks:        | |
remarks:        | We will accept any routes offered including TRANSIT! |
remarks:        | |
remarks:        | We will update our aut-num object in the RIPE Whois |
remarks:        | Database and kindly request you to update yours |
remarks:        | |
remarks:        | We would prefer not to enter into a peering contract |
remarks:        | |
remarks:        | In the event of problems due to leaked advertisements |
remarks:        | it is our policy to shut down peerings and ask |
remarks:        | questions later. |
remarks:        | |
remarks:        | We may tag our announcements with the NO_EXPORT or |
remarks:        | other communities, please honour these if set. |
remarks:        | |
remarks:        ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
remarks:        | |
remarks:        | * AMS-IX - IPv4 * |
remarks:        | |
remarks:        | 80.249.208.68 - Equinix AM3 |
remarks:        | 80.249.208.71 - Telecity AMS5 |
remarks:        | |
remarks:        | * AMS-IX - IPv6 * |
remarks:        | |
remarks:        | 2001:7F8:1::A500:3333:1 - Equinix AM3 |
remarks:        | 2001:7F8:1::A500:3333:2 - Telecity AMS5 |
remarks:        | |
remarks:        ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
remarks:        | |
remarks:        | Telephone: +31 20 535 4444 |
remarks:        | Fax: +31 20 535 4445 |
remarks:        | Abuse: abuse@ripe.net |
remarks:        | Peering: peering@ripe.net |
remarks:        | Operations/NOC: ops@ripe.net |
remarks:        | Info: https://www.ripe.net/ |
remarks:        | |
remarks:        ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
remarks:
remarks:
remarks:        +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
remarks:        | PRIVATE-TRANSIT-V4 |
remarks:        +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
remarks:        | Private transit peering |
remarks:        +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
remarks:
remarks:        +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
remarks:        | TeliaSonera |
remarks:        +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
import:         from AS1299 62.115.12.201 at 62.115.12.202 action pref=100; accept ANY
export:         to AS1299 62.115.12.201 at 62.115.12.202 announce AS-RIPENCC
import:         from AS1299 62.115.12.205 at 62.115.12.206 action pref=100; accept ANY
export:         to AS1299 62.115.12.205 at 62.115.12.206 announce AS-RIPENCC
remarks:
remarks:        +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
remarks:        | AMS-IX-TRANSIT |
remarks:        ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

What AS3333 announces

Prefixes originated by AS3333 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
6
IPv6 prefixes
2
IPv4 addresses
4,608 (18 /24s)
RPKI valid
8 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS3333
13
With an IRR route object
7 87%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

Who AS3333 is reached through

The AS just before AS3333 in the paths our looking glass collectors hold, for 8 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.

Provider authorization

AS3333 publishes no ASPA of its own. 1 AS name it as a provider in theirs. Check a path.

The 1 ASes that name AS3333 as a provider