Network · data from 2026-11-12
AS153622 MADINAIT-AS-AP - Madina IT
Registry name: MADINAIT-AS-AP - Madina IT, BD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS153622, 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.
| 174.140.226.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 185.218.20.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 193.32.204.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS153622 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 4 are in fix.csv.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 174.140.226.0/24 | ROAs covering it name AS834, AS17252, not AS153622. If AS153622 should announce it, add a ROA for AS153622. |
| Route object: none | 174.140.226.0/24 | Route objects for it name AS834. Add a route object with origin AS153622 in the RIR database for the space. |
| ROA: origin | 185.218.20.0/24 | ROAs covering it name AS834, not AS153622. If AS153622 should announce it, add a ROA for AS153622. |
| Route object: none | 185.218.20.0/24 | Route objects for it name AS834. Add a route object with origin AS153622 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS153622 is announced.
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.