bgpreport

Network · data from 2026-11-12

AS268219 SDG TELECOM E SERVICOS

Registry name: AS268219 - SDG TELECOM E SERVICOS LTDA - ME, BR · PeeringDB

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

Announced routes

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

45.236.12.1/32 Valid Nonecovered by 45.236.12.0/24 1 0%low visibility 2
45.236.12.145/32 Valid Nonecovered by 45.236.12.0/24 1 0%low visibility 2
45.236.13.17/32 Valid Nonecovered by 45.236.13.0/24 1 0%low visibility 2
45.236.13.93/32 Valid Nonecovered by 45.236.13.0/24 1 0%low visibility 2
45.236.12.0/22 Valid Other IRR onlyRADB, TC 670 100% 67
2804:4dc8::/32 Valid Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS268219'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 14 are in fix.csv.

  • Route object: none4
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none45.236.12.1/32No route object for it. A route object for 45.236.12.0/24 with origin AS268219 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS268219 in the RIR database for the space.1 of 673
Route object: none45.236.12.145/32No route object for it. A route object for 45.236.12.0/24 with origin AS268219 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS268219 in the RIR database for the space.1 of 673
Route object: none45.236.13.17/32No route object for it. A route object for 45.236.13.0/24 with origin AS268219 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS268219 in the RIR database for the space.1 of 673
Route object: none45.236.13.93/32No route object for it. A route object for 45.236.13.0/24 with origin AS268219 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS268219 in the RIR database for the space.1 of 673
Route object: RIR45.236.12.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:4dc8::/32Route 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 AS268219 whose prefix no peer sees AS268219 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.236.12.0/23RADB, TCValid
45.236.12.0/24TCValid
45.236.13.0/24TCValid
45.236.14.0/23RADB, TCValid
45.236.14.0/24TCValid
45.236.15.0/24TCValid
2804:4dc8::/33TCValid
2804:4dc8:8000::/33TCValid

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.