bgpreport

Network · data from 2026-11-12

AS210554 METEORCLOUD

Registry name: METEORCLOUD Meteor Cloud LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210554, 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.

151.243.24.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a14:67c1:b300::/40 Valid Other origin only 636 100% 67
2.27.112.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
79.182.128.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
74.0.5.0/24 Valid RIR databaseARIN, RADB 671 100% 67
151.244.40.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
198.1.195.0/24 Valid RIR databaseARIN, RADB 671 100% 67
2a0c:b641:390::/44 Valid RIR databaseRIPE 635 100% 67
2a13:9500:153::/48 Valid RIR databaseRIPE 635 100% 67
2a13:9500:154::/48 Valid RIR databaseRIPE 635 100% 67
2a13:9500:160::/48 Valid RIR databaseRIPE 635 100% 67
82.38.28.0/24 Valid RIR databaseRADB, RIPE 1 0%low visibility 1

AS-SET

AS210554's PeeringDB record names no 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: origin1
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin151.243.24.0/24ROAs covering it name AS834, not AS210554. If AS210554 should announce it, add a ROA for AS210554.2 of 673
Route object: none151.243.24.0/24Route objects for it name AS834. Add a route object with origin AS210554 in the RIR database for the space.2 of 673
Route object: none2a14:67c1:b300::/40Route objects for it name AS210940. Add a route object with origin AS210554 in the RIR database for the space.636 of 636

Route objects not announced

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

45.157.16.0/24RADB, RIPEValid
198.89.99.0/24ARINValid

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.