bgpreport

Network · data from 2026-11-12

AS152674 MARVELWEBHOST-AS-AP - Marvel Web Host

Registry name: MARVELWEBHOST-AS-AP - Marvel Web Host, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS152674, 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.
203.28.252.0/24 Invalid: origin Other origin only 2 0%low visibility 2
203.28.253.0/24 Invalid: origin Other origin only 2 0%low visibility 2

AS-SET

AS152674 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 5 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin203.28.252.0/24ROAs covering it name AS150180, not AS152674. If AS152674 should announce it, add a ROA for AS152674.2 of 673
Route object: none203.28.252.0/24Route objects for it name AS150180. Add a route object with origin AS152674 in the RIR database for the space.2 of 673
ROA: origin203.28.253.0/24ROAs covering it name AS150180, not AS152674. If AS152674 should announce it, add a ROA for AS152674.2 of 673
Route object: none203.28.253.0/24Route objects for it name AS150180. Add a route object with origin AS152674 in the RIR database for the space.2 of 673

Route objects not announced

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

2001:df3:9fc0::/48APNICValid

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.