AS50673 Serverius Holding B.V.
AS50673 (Serverius-as) is registered to Serverius Holding B.V. in NL, through RIPE. It originates 85 prefixes in the global routing table.
Who holds AS50673
Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.
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 'AS50220 - AS50841'
as-block: AS50220 - AS50841
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: 2024-08-12T14:10:44Z
last-modified: 2024-08-12T14:10:44Z
source: RIPE
% Information related to 'AS50673'
% Abuse contact for 'AS50673' is 'abuse@serverius.net'
aut-num: AS50673
as-name: Serverius-as
org: ORG-SHB2-RIPE
remarks: ------------------------------------------------
remarks: IP Transits
remarks: ------------------------------------------------
remarks: Liberty Global
export: to AS6830 announce AS-SERVERIUS
import: from AS6830 accept ANY
remarks: RETN Ltd.
export: to AS9002 announce AS-SERVERIUS
import: from AS9002 accept ANY
remarks: Core-BackBone
import: from AS33891 accept ANY
export: to AS33891 announce AS-SERVERIUS
remarks: Cogent
import: from AS174 accept ANY
export: to AS174 announce AS-SERVERIUS
remarks: TATA COMMUNICATIONS
import: from AS6453 accept ANY
export: to AS6453 announce AS-SERVERIUS
remarks: SPARKLE TELECOM (SEABONE)
import: from AS6762 accept ANY
remarks: to AS6762 announce AS-SERVERIUS
remarks: ------------------------------------------------
remarks: Exchange Points
remarks: ------------------------------------------------
remarks: SPEED-IX
import: from AS41441 accept ANY
export: to AS41441 announce AS-SERVERIUS
remarks: AMS-IX
import: from AS6777 accept ANY
export: to AS6777 action community .= { 6777:6777 }; announce AS-SERVERIUS
import-via: AS6777 from AS-ANY accept ANY
export-via: AS6777 to AS-ANY announce AS-SERVERIUS
remarks: NL-IX
import: from AS34307 accept ANY
export: to AS34307 announce AS-SERVERIUS
remarks: DATA-IX
import: from AS50952 accept ANY
export: to AS50952 announce AS-SERVERIUS
remarks: DATA-IX-UA
import: from AS50952 accept ANY
export: to AS50952 announce AS-SERVERIUS
remarks: DF-IX
import: from AS49917 accept ANY
export: to AS49917 announce AS-SERVERIUS
remarks: ------------------------------------------------
remarks: Private Peerings
remarks: ------------------------------------------------
remarks: Amazon
import: from AS16509 accept AS-AMAZON
export: to AS16509 announce AS-SERVERIUS
remarks: Google
import: from AS15169 accept AS-GOOGLE
export: to AS15169 announce AS-SERVERIUS
remarks: OVH
import: from AS16276 accept AS-OVH
export: to AS16276 announce AS-SERVERIUS
remarks: Hetzner Online GmbH
import: from AS24940 accept AS-HETZNER
export: to AS24940 announce AS-SERVERIUS
remarks: NFOrce Entertainment BV
import: from AS43350 accept AS-NFORCE
export: to AS43350 announce AS-SERVERIUS
remarks: LeaseWeb Network B.V.
import: from AS16265 accept AS-LEASEWEB
export: to AS16265 announce AS-SERVERIUS
remarks: i3D Interactive
import: from AS49544 accept AS-INTERACTIVE3D
export: to AS49544 announce AS-SERVERIUS
remarks: Worldstream
import: from AS49981 accept AS-WORLDSTREAM
export: to AS49981 announce AS-SERVERIUS
remarks: XS4ALL Internet BV
import: from AS3265 accept AS-ACCESSFORALL
export: to AS3265 announce AS-SERVERIUS
remarks: Akamai International B.V.
import: from AS20940 accept AS-AKAMAI
export: to AS20940 announce AS-SERVEWhat AS50673 announces
Prefixes originated by AS50673 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).
Announced prefixes
Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.
RPKI valid RPKI invalid no ROA covers it
Who AS50673 is reached through
The AS just before AS50673 in the paths our looking glass collectors hold, for 60 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.
Provider authorization
AS50673 publishes no ASPA of its own. 6 ASes name it as a provider in theirs. Check a path.
The 6 ASes that name AS50673 as a provider
Routing registry objects
From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.
| Source | as-name | Maintained by |
|---|---|---|
| RIPE | Serverius-as | RIPE-NCC-END-MNT, SERVERIUS-MNT |
Route objects with origin AS50673: RIPE 116 · RADB 6 · ARIN 1 · NTTCOM 1