bgpreport

Network · data from 2026-11-12

AS153376 Brick Eduoctition And Safety Compoters' Network

Registry name: BRNET-AS-AP - Jilin Province Brick Business Service Limited, CN · PeeringDB

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

Announced routes

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

44.32.191.0/24 No ROA Other IRR onlyRADB 669 99% 67
2a14:7586:6300::/44 No ROA RIR databaseRIPE 1 0%low visibility 1
2406:840:fead::/48 Valid RIR databaseAPNIC 635 100% 70
2a12:cb46:6300::/40 Valid RIR databaseRIPE 635 100% 70
2a12:cb46:6400::/44 Valid RIR databaseRIPE 635 100% 69
2406:840:e600::/44 Valid RIR databaseAPNIC 634 100% 69
2602:f92a:a468::/48 Valid RIR databaseARIN 634 100% 69
2a0f:1cc5:10::/46 Valid RIR databaseRIPE 634 100% 69
2a0f:1cc5:2550::/48 Valid RIR databaseRIPE 634 100% 69
2a12:cb46:6000::/40 Valid RIR databaseRIPE 634 100% 69
2a12:cb46:6100::/40 Valid RIR databaseRIPE 634 100% 69
2a12:cb46:6200::/40 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS153376: AS153376:AS-DOWNSTREAM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS153376 isn't in the set, or no route object for AS153376 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS153376 in itNot covered
AS153376:AS-DOWNSTREAM APNIC 53101 Yes 0

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

  • ROA: none2
  • Route object: RIR1
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
ROA: none44.32.191.0/24No ROA covers it. Add a ROA for AS153376, maxLength 24.669 of 673
Route object: RIR44.32.191.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2a14:7586:6300::/44No ROA covers it. Add a ROA for AS153376, maxLength 44.1 of 636

Route objects not announced

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

2406:840:e600::/45APNICValid
2406:840:e600::/46APNICValid
2406:840:e600::/47APNICValid
2406:840:e600::/48APNICValid
2406:840:e601::/48APNICValid
2406:840:e602::/47APNICValid
2406:840:e602::/48APNICValid
2406:840:e603::/48APNICValid
2406:840:e604::/46APNICValid
2406:840:e604::/47APNICValid
2406:840:e604::/48APNICValid
2406:840:e605::/48APNICValid
2406:840:e606::/47APNICValid
2406:840:e606::/48APNICValid
2406:840:e607::/48APNICValid
2406:840:e608::/45APNICValid
2406:840:e608::/46APNICValid
2406:840:e608::/47APNICValid
2406:840:e608::/48APNICValid
2406:840:e609::/48APNICValid
2406:840:e60a::/47APNICValid
2406:840:e60a::/48APNICValid
2406:840:e60b::/48APNICValid
2406:840:e60c::/46APNICValid
2406:840:e60c::/47APNICValid
2406:840:e60c::/48APNICValid
2406:840:e60d::/48APNICValid
2406:840:e60e::/47APNICValid
2406:840:e60e::/48APNICValid
2406:840:e60f::/48APNICValid
2a0f:9400:6110::/48RIPEValid
2a12:cb46:6410::/44RIPEValid
2a13:9500:195::/48RIPEValid

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.