bgpreport

Network · data from 2026-11-12

AS52847 AS52847 - Master Telecom

Registry name: AS52847 - Master Telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52847, 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.
177.66.148.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
177.66.148.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
177.66.148.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
177.66.149.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
177.66.150.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
177.66.150.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
177.66.151.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
2804:1084::/32 Valid Other IRR onlyALTDB, RADB, TC 634 100% 67
2804:1084:8000::/33 Valid Other IRR onlyRADB, TC 634 100% 67

AS-SET

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

  • Route object: RIR9
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: RIR177.66.148.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.66.148.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.66.148.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.66.149.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.66.150.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.66.150.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.66.151.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:1084::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:1084:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2804:1084::/33RADB, TCValid
2804:1084::/34RADB, TCValid
2804:1084::/35TCValid
2804:1084:2000::/35TCValid
2804:1084:4000::/34RADB, TCValid
2804:1084:4000::/35TCValid
2804:1084:6000::/35TCValid
2804:1084:8000::/34RADB, TCValid
2804:1084:8000::/35TCValid
2804:1084:a000::/35TCValid
2804:1084:c000::/34RADB, TCValid
2804:1084:c000::/35TCValid
2804:1084:e000::/35TCValid

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.