AS48200 Opteamax GmbH
AS48200 (OPTEAMAX-AS) is registered to Opteamax GmbH in DE, through RIPE. It originates 5 prefixes in the global routing table.
Who holds AS48200
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 'AS47870 - AS49384' as-block: AS47870 - AS49384 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: 2025-07-09T08:51:07Z last-modified: 2025-07-09T08:51:07Z source: RIPE % Information related to 'AS48200' % Abuse contact for 'AS48200' is 'abuse@opteamax.de' aut-num: AS48200 as-name: OPTEAMAX-AS org: ORG-OG38-RIPE remarks: ******************************************************* remarks: ======================================================= remarks: UPSTREAMS: remarks: ======================================================= remarks: * TELIA ID: 1 * mp-import: afi ipv6.unicast from AS1299 accept ANY mp-export: afi ipv6.unicast to AS1299 announce AS48200:AS-OPTEAMAX import: from AS1299 accept ANY export: to AS1299 announce AS48200:AS-OPTEAMAX-V4 remarks: ------------------------------------------------------- remarks: * NTT ID: 2 * mp-import: afi ipv6.unicast from AS2914 accept ANY mp-export: afi ipv6.unicast to AS2914 announce AS48200:AS-OPTEAMAX import: from AS2914 accept ANY export: to AS2914 announce AS48200:AS-OPTEAMAX-V4 remarks: ------------------------------------------------------- remarks: * DTAG ID: 3 * mp-import: afi ipv6.unicast from AS3320 accept ANY mp-export: afi ipv6.unicast to AS3320 announce AS48200:AS-OPTEAMAX import: from AS3320 accept ANY export: to AS3320 announce AS48200:AS-OPTEAMAX-V4 remarks: ------------------------------------------------------- remarks: * CHINA-TELECOM ID: 4 * import: from AS4809 accept ANY export: to AS4809 announce AS48200:AS-OPTEAMAX-V4 remarks: ------------------------------------------------------- remarks: * TI Sparkle ID: 6 * mp-import: afi ipv6.unicast from AS6762 accept ANY mp-export: afi ipv6.unicast to AS6762 announce AS48200:AS-OPTEAMAX import: from AS6762 accept ANY export: to AS6762 announce AS48200:AS-OPTEAMAX-V4 remarks: ------------------------------------------------------- remarks: ======================================================= remarks: DOWNSTREAMS: remarks: ======================================================= remarks: * ADESTIS ID: 9984 * mp-import: afi ipv6.unicast from AS204053 accept AS-ADESTIS mp-export: afi ipv6.unicast to AS204053 announce ANY import: from AS204053 accept AS-ADESTIS export: to AS204053 announce ANY remarks: ------------------------------------------------------- remarks: * WEBERCLOUD ID: 9987 * mp-import: afi ipv6.unicast from AS35710 accept AS-WEBERCLOUD mp-export: afi ipv6.unicast to AS35710 announce ANY import: from AS35710 accept AS-WEBERCLOUD export: to AS35710 announce ANY remarks: ------------------------------------------------------- remarks: * ROCKINGHOSTER ID: 9988 * mp-import: afi ipv6.unicast from AS202298 accept AS202298 mp-export: afi ipv6.unicast to AS202298 announce ANY import: from AS202298 accept AS202298 export: to AS202298 announce ANY remarks: ------------------------------------------------------- remarks: * msg systems ag ID: 9991 * import: from AS43868 accept AS43868 export: to AS43868 announce ANY remarks: ------------------------------------------------------- remarks: * WEBHOSTER ID: 9992 * mp-import: afi ipv6.unicast from AS200548 accept AS-WEBHOSTER mp-export: afi ipv6.unicast to AS200548 announce ANY import:
What AS48200 announces
Prefixes originated by AS48200 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 AS48200 is reached through
The AS just before AS48200 in the paths our looking glass collectors hold, for 5 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.
Routing registry objects
From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.
| Source | as-name | Maintained by |
|---|---|---|
| RIPE | OPTEAMAX-AS | OPTEAMAX-MNT, RIPE-NCC-END-MNT |
Route objects with origin AS48200: RIPE 9