bgpreport

Network · data from 2026-11-12

AS55154 MADGEN-01 - Madgenius.com

Registry name: MADGEN-01 - Madgenius.com, US · not in PeeringDB

2IPv4 routes 50.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
52Route objects not announced registered with origin AS55154, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55154, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

192.119.171.0/24 No ROA RIR databaseARIN, RADB 1 0%low visibility 1
198.50.31.0/24 Valid RIR databaseARIN 1 0%low visibility 1

AS-SET

AS55154 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 53 are in fix.csv.

  • ROA: none1
  • Route object: not announced52
ChangePrefix or setDetailFull-table peers
ROA: none192.119.171.0/24No ROA covers it. Add a ROA for AS55154, maxLength 24.1 of 673

Route objects not announced

Route objects with origin AS55154 whose prefix no peer sees AS55154 announce. Many are kept on purpose (backup routes, space announced only in some places).

66.63.170.0/24ARINInvalid: origin
67.214.179.0/24ARINValid
67.215.228.0/24ARINInvalid: origin
67.215.248.0/24ARINInvalid: origin
72.11.138.0/24ARINInvalid: origin
74.80.178.0/24ARINInvalid: origin
74.119.217.0/24ARINValid
74.122.196.0/24ARINValid
96.44.150.0/24ARINInvalid: origin
102.135.32.0/24AFRINICValid
102.135.33.0/24AFRINICValid
102.135.34.0/24AFRINICValid
102.135.35.0/24AFRINICValid
102.135.36.0/24AFRINICValid
102.135.38.0/24AFRINICValid
102.135.50.0/24AFRINICNo ROA
102.135.51.0/24AFRINICNo ROA
102.135.55.0/24AFRINICNo ROA
102.135.56.0/24AFRINICNo ROA
102.135.59.0/24AFRINICNo ROA
102.135.73.0/24AFRINICNo ROA
104.129.51.0/24ARINInvalid: origin
104.223.12.0/24ARINInvalid: origin
104.223.64.0/24ARINInvalid: origin
104.223.80.0/24ARINValid
104.223.114.0/24ARINInvalid: origin
104.233.60.0/24RIPEInvalid: origin
104.233.61.0/24RIPEInvalid: origin
104.233.62.0/24RIPEInvalid: origin
104.234.85.0/24ARINInvalid: origin
107.150.1.0/24ARINInvalid: origin
107.150.6.0/24ARINInvalid: origin
109.203.180.0/22RIPEValid
111.119.165.0/24APNICInvalid: origin
116.90.115.0/24APNICValid
139.177.154.0/24ARINInvalid: origin
154.16.46.0/24AFRINICInvalid: origin
155.94.209.0/24ARINInvalid: origin
172.94.72.0/24ARINValid
173.243.116.0/24ARINValid
185.100.120.0/24ALTDBNo ROA
192.119.168.0/24ARINNo ROA
192.119.169.0/24ARINNo ROA
192.119.170.0/24ARINNo ROA
192.119.172.0/24ARINNo ROA
192.119.173.0/24ARINNo ROA
192.119.174.0/24ARINNo ROA
192.119.175.0/24ARINNo ROA
198.46.1.0/24ALTDBNo ROA
198.50.30.0/24ARINValid
199.96.80.0/24ARINValid
204.152.209.0/24ARINInvalid: origin

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.