AS8767 M-net Telekommunikations GmbH
AS8767 (MNET-AS) is registered to M-net Telekommunikations GmbH in DE, through RIPE. It originates 76 prefixes in the global routing table.
Who holds AS8767
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 'AS8525 - AS8769' as-block: AS8525 - AS8769 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 % Information related to 'AS8767' % Abuse contact for 'AS8767' is 'abuse@m-online.net' aut-num: AS8767 as-name: MNET-AS descr: Germany remarks: M-net AS org: ORG-MTG1-RIPE remarks: ==================================================== import: from AS42 action pref=80; accept AS-PCH export: to AS42 announce AS-MNETDE remarks: ==================================================== import: from AS553 action pref=80; accept AS-BELWUE export: to AS553 announce AS-MNETDE remarks: ==================================================== import: from AS680 action pref=80; accept AS680:AS-DFNTOWINISP export: to AS680 announce AS-MNETDE remarks: ==================================================== import: from AS714 action pref=80; accept AS-APPLE export: to AS714 announce AS-MNETDE remarks: ==================================================== import: from AS1200 action pref=80; accept AS1200 export: to AS1200 announce AS-MNETDE remarks: ==================================================== import: from AS1248 action pref=80; accept AS-HERE export: to AS1248 announce AS-MNETDE remarks: ==================================================== import: from AS1267 action pref=80; accept AS-WINDTRE export: to AS1267 announce AS-MNETDE remarks: ==================================================== import: from AS1299 action pref=100; accept ANY export: to AS1299 announce AS-MNETDE remarks: ==================================================== import: from AS1547 action pref=80; accept AS-IDK export: to AS1547 announce AS-MNETDE remarks: ==================================================== import: from AS1764 action pref=80; accept AS-NEXTLAYER export: to AS1764 announce AS-MNETDE remarks: ==================================================== import: from AS1828 action pref=80; accept AS-UNITAS export: to AS1828 announce AS-MNETDE remarks: ==================================================== import: from AS2119 action pref=80; accept AS-TELENOR export: to AS2119 announce AS-MNETDE remarks: ==================================================== import: from AS2484 action pref=80; accept AS-AFNIC export: to AS2484 announce AS-MNETDE remarks: ==================================================== import: from AS2559 action pref=80; accept AS-VISA export: to AS2559 announce AS-MNETDE remarks: ==================================================== import: from AS2603 action pref=80; accept AS-NORDUNET export: to AS2603 announce AS-MNETDE remarks: ==================================================== import: from AS2686 action pref=80; accept AS-IGNEMEA export: to AS2686 announce AS-MNETDE remarks: ==================================================== import: from AS2860 action pref=80; accept AS-NOVIS export: to AS2860 announce AS-MNETDE remarks: ==================================================== import: from AS2906 action pref=80; accept AS-NFLX export: to AS2906 announce AS-MNETDE remarks: ==================================================== import: from AS2914 action pref=1
What AS8767 announces
Prefixes originated by AS8767 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 AS8767 is reached through
The AS just before AS8767 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
AS8767 publishes no ASPA of its own. 2 ASes name it as a provider in theirs. Check a path.
The 2 ASes that name AS8767 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 | MNET-AS | MNET-MNT, RIPE-NCC-END-MNT |
Route objects with origin AS8767: RIPE 109 · ARIN 2